Hi Sherwin,

Thank you for posting.

While Okta does not have an integration with Django, it does support it with its SDK. Here is the documentation for this:

https://developer.okta.com/code/python/#python-samples

As per the scopes, it does. here is the documentation or that part as well.

https://developer.okta.com/docs/guides/customize-authz-server/create-scopes/

Hi Daniel,

I'm aware of python sdk but as i went through the code example you are using async where django doesn't support it, even if I user async.io I couldn't able to integrate your sdk successfully, so I switched from sdk to your rest api, using your /v1/authorize and /v1/token/ i'm getting access token successfully.

Now the problem is when i'm using normal okta username password for login, I'm getting the access token and can validate whether the token is valid or not but when i'm using social identity providers with okta i'm getting the access token but i cant able to decode it successfully

The reason for failing identity providers token decoding:

1. Audience and issuers are changing while using social login (i.e) for email password auth the default authorization server's issuer and audience are used but if i dig what is coming in token is that the issuer and audience of the application single sign-on page
2. Due to the dynamic changing of the token and audience between different auth method I can't able to write a generalized Authentication class for protecting my endpoints
3. If I hard code the audience for the identity provider login it is throwing me a error called JWKS_URI not found

The things I need now, is a generalized way to check the validity and payload of the access token issued by your server (both normal login's as well as identity provider's access token)

It will be easy if any of your developer can arrange a quick call to sort of my company's problem also it will be a added advantage for keeping a documentation for integrating django restapi with okta.

Thank you.