Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

urn:ietf:params:oauth:grant-type:saml2-bearer Not included in OAuthGrantType #298

Closed
bfrisbie-brex opened this issue May 26, 2022 · 10 comments · Fixed by #317
Closed

urn:ietf:params:oauth:grant-type:saml2-bearer Not included in OAuthGrantType #298

bfrisbie-brex opened this issue May 26, 2022 · 10 comments · Fixed by #317

Comments

@bfrisbie-brex
Copy link

Using Postman, I can create an OAuth2 Client with urn:ietf:params:oauth:grant-type:saml2-bearer as one of the grant_types.

However, that is missing from OAuthGrantType here, and thus I can't create such an OAuth2 Client using the Python SDK.

@laura-rodriguez
Copy link
Collaborator

laura-rodriguez commented Jun 7, 2022

Hi @bfrisbie-brex,

Thanks for your patience. I'll file an internal ticket for our team to review and prioritize. Are you currently blocked by this or you have a workaround?

Internal Ref: OKTA-505019

@bfrisbie-brex
Copy link
Author

bfrisbie-brex commented Jun 15, 2022

Hi @laura-rodriguez , I'm sorry for not responding sooner, I overlooked your reply.

Yes, this issue is blocking my team from migrating from our existing OAuth Server to Okta's API Access Management solution.

Do you think your team might be able to address this issue within the next several weeks?

@bfrisbie-brex
Copy link
Author

Hi @laura-rodriguez , checking in on this again: Do you think your team might be able to address this issue within the next several weeks?

@laura-rodriguez
Copy link
Collaborator

Hi @bfrisbie-brex,

Thanks for your patience. Let me ask internally and we'll get back to you. Thank you!

@laura-rodriguez
Copy link
Collaborator

Hey @bfrisbie-brex,

Just to get you unblocked while I get a response from the team, you can consider making the request manually using the SDK as explained here.

Let me know if this workaround works for you in the meantime.

@bfrisbie-brex
Copy link
Author

Hi @laura-rodriguez , yes, that has been our plan from the beginning.

The reason I asked if the Okta team is able to address this issue in the next few weeks is to determine if we should directly request the API directly as a "workaround" for this bug in the python SDK, or if we can expect this bug to be fixed sooner rather than later.

@laura-rodriguez
Copy link
Collaborator

Hey @bfrisbie-brex ,
I understand this is a low-priority bug since there's a workaround, so I suggest you keep making the manual request in the meantime.

@bfrisbie-brex
Copy link
Author

@laura-rodriguez to be clear, we haven't written any code to make the manual request yet, in the hopes Okta will fix its bugs in a timely manner.

It would be nice if Okta could provide a time estimate on when this bug will be addressed.

@bfrisbie-brex
Copy link
Author

bfrisbie-brex commented Sep 7, 2022

Hi @laura-rodriguez , this bug is becoming higher priority for our team, as we have a python script to migrate dozens of OAuth Clients over to Okta, and calling the API individually for each client is not practical.

Is there any way the priority of this issue/request can be increased?

On the surface, it doesn't seem like it should take a massive engineering effort to fix.

@laura-rodriguez
Copy link
Collaborator

Hey @bfrisbie-brex,
I truly apologize for the inconvenience. We are experiencing some challenges in addressing Python Github issues. Please bear with us while we work to improve this process and SDK by addressing your feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants