Add-on for FinTS

The Add-on for FinTS is based on the open source FinTS library for Python (https://python-fints.readthedocs.io/en/latest/index.html#) and allows you to collect various different data from your bank account. I've created this TA to observe my rental-accounts and gain insights of my personal cashflow. Altough the FinTS library has been implemented the way the FinTS3.0 protocol was designed, not every bank supports it yet the way they should. For issues or troubleshooting regarding the connectivity I suggest you to look into the Git Repo of the FinTS project (https://github.com/raphaelm/python-fints). The Add-on provides only management dashboards for online banking accounts, input types and TAN authentication. It contains no analyzation, visualization or alerts of the data. The collected data is ingested as JSON, so it should be usable without any additional field extractions. Accounts: The Add-on is based on accounts, they are the first you need to setup. They can be configured in the fints_accounts.conf or using the account management dashboard. Your online banking account requires several parameter to be used like your targets bank Bankleitzahl (BLZ), your banks HBCI server address (Endpoint), if you have multiple numbers under your account your target international bank account number (IBAN) and of course your online banking credentials (User, PIN/Password). The PIN will be stored encrypted (using the splunk.secret) in the passwords.conf. Inputs: The Add-on provides four different inputs which are basically the getters from the FinTS library. Each input can be configured for each account independently. They can be configured in the inputs.conf or using the inputs management dashboard. Each input only requires an account and an input name. To avoid redundant ingestion, I suggest that you use the default cron schedule (see below for suggestions). Also note that the transaction input can query more than one day, however due to consistency I've set it to the last day, so that each input can run once a day. I plan to make it more configurable in future releases. Also I have no available accounts with holdings. So I don't know what this input would return. Feel free to contact me for further development in this area. TAN Authentication: For the first time and from time to time it is required to authenticate your access with a Transaktionsnummer (TAN). To authenticate your accounts I've implemented an authentication management dashboard. Since the TAN can be generated on various ways, I try to forward the TAN challenge to the webpage. However my banks support only a few TAN methods, so my development in this area is limited. Currently tested and supported are photoTAN, pushTAN and mobileTAN. Feel free to develope further in this area with your own TAN method. Suggestion for input frequency by type: Balance: 0 1 * * * (daily) Transaction: 0 1 * * * (daily) Bankinformation: 0 0 1 * * (monthly) Holding: 0 0 1 * * (monthly)