-
Notifications
You must be signed in to change notification settings - Fork 7
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
Feature: OKTA broker #172
Comments
This would be a useful integration. |
Hi @shiv-tyagi, that's a very big task. I suggest you work on something a bit smaller. I looked through our open issues and found these two which might be a better fit:
Let me know if any of those sound interesting to you and I'll explain more on the ticket about what needs to be done. |
I would like to work on this issue. I went through the comments and got an idea of what needs to be done. Anything else you would like to emphasise or should I do a PR and ask you for a feedback on it? |
I replied in ubuntu/authd#620 (comment) |
Is there an existing request for this feature?
Describe the feature
Since OKTA is one of most frequently used by enterprise would it possible to create a broker for it?
Describe the ideal solution
Broker with similiar workflow as Entra ID
Alternatives and current workarounds
Currently it is possible to sync OKTA to Entra and use that to get authentication working but this only adds one additional system which optimally could be eliminated.
System information and logs
No response
Relevant information
No response
Double check your logs
The text was updated successfully, but these errors were encountered: