I'm currently using supertokens for auth for our customers to log into our app. Our customers will need to input their credentials to certain 3rd party systems in order to use those as integrations. These are per company that we sell to, not per user. It doesn't seem like Supertokens would support a use case like that which is more of general secrets storing than specific application auth. Just wanted to confirm that is correct and we should build our own separate credentials manager for this use case.

hey @arnmishra are you talking about a multi tenancy use case wherein a specific customer of yours will require their employees to login to your app via their identify provider? If yes, this is a feature we will be releasing shortly (in a few weeks)

ah no, what I'm talking about is 3rd party integrations. for example, if you want to link two services together, you'd need to provide the application auth. i.e. if you were to authenticate a 2 way read integration with your bank for a financial management tool, you'd need to provide you bank oauth token or credentials to the financial management tool. if I was building that financial management tool, I now need to store that customer's token or credentials securely for their bank. Supertokens would obviously store the credentials for the user logging into the financial management tool, but would there also be a way to store the user's bank creds/token somewhere?

Ah i see. You could store it in the user's session and refresh those tokens in the session refreshing API, but other than that, it's up to you how to handle storage and refreshing of those credentials.

Sounds good, thanks!