I don't think a settings.py script is ideal for a library. This pattern works pretty well for a Django application because the developers will just edit as needed. But consumers of the Custos Python SDK won't have a good way to edit this as needed. I think instead we could either:

• Have a Settings class with default values and the client can instantiate it and override those values and then pass in that instance as a parameter or maybe register it
• Read settings from a settings file. You can use the configparser to load an .ini style config file. There could be a default location for the file and/or the location of the file could be passed in as a parameter

Using configparser to load .ini file. Location of the configuration file will be passed as an argument

I think you'll need a method to initiate the redirect flow, unless you are planning on doing that in a separate PR.

Not sure about what the redirect flow is. I have added 3 flows 1) user_authentication: when user name and password are given 2) account_authentication: when the service account client id and client credentials are supplied 3) refresh token: when user/account is already authenticated
My understanding is the redirect flow is when clientId and client credentials are supplied ie option2 account_authentication. Please correct me if I am wrong.

There are two parts to the redirect flow:

1. Redirect to the IdP
2. Process the response

You've implemented the second one. We could also have a utility code for generating the approach redirection URL for initiating the first part.

In the Django portal, setting up the redirect URL is handled here: https://github.com/apache/airavata-django-portal/blob/master/django_airavata/apps/auth/views.py#L42