-
Notifications
You must be signed in to change notification settings - Fork 731
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
Support for creating OAuth 2.0 clients inside B2B organizations for B2B API access #21208
Open
ShanChathusanda93 opened this issue
Oct 1, 2024
· 0 comments
· May be fixed by wso2/carbon-identity-framework#6185, wso2/carbon-identity-framework#6194 or wso2/charon#417
Open
Support for creating OAuth 2.0 clients inside B2B organizations for B2B API access #21208
ShanChathusanda93 opened this issue
Oct 1, 2024
· 0 comments
· May be fixed by wso2/carbon-identity-framework#6185, wso2/carbon-identity-framework#6194 or wso2/charon#417
Labels
Comments
This was referenced Oct 9, 2024
This was referenced Nov 1, 2024
This was referenced Dec 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Many organizations expose their capabilities as APIs to external organizations. These are generally referred to as B2B APIs. External organizations who wish to consume these APIs, would need subscribe to these APIs and consume them. As part of the subscription process an OAuth 2.0 client is created in the authorization server. If WSO2 Identity Server is acting as the OAuth 2.0 authorization server in this case, based on the organization management model it has, these OAuth 2.0 clients need to be created inside a B2B sub-orgnanization dedicated to that external organization, due to clear separation of OAuth 2.0 client's delegated management requirement.
Describe the solution you would prefer
It should be as simple as enabling the application management capability in the B2B sub-organization. However, when accessing these applications they should not be treated any different to applications created in the root-organization. They are created in the sub-organization only for the purpose of administration.
The text was updated successfully, but these errors were encountered: