Description:
Currently, the EI does not have a way inbuilt to handle OAuth 2.0 flows. We can still manually implement any of these authorization flows in Synapse but we do not have a specific abstracted component such as a connector to achieve this. For example, we have manually implemented an OAuth 2.0 Authorization code flow in [1].
It would be ideal there is a connector/mediator where the user can provide OAuth2.0 related parameters such as client ID, client secret, token endpoint etc. and execute operations such as token exchange and token refreshing.
Our OAuth mediator cannot accomplish as it is designed only to communicate with the WSO2 IS and verify a set of given user credentials.
falconmfm
commented
3 years ago
Description: Currently, the EI does not have a way inbuilt to handle OAuth 2.0 flows. We can still manually implement any of these authorization flows in Synapse but we do not have a specific abstracted component such as a connector to achieve this. For example, we have manually implemented an OAuth 2.0 Authorization code flow in [1].
It would be ideal there is a connector/mediator where the user can provide OAuth2.0 related parameters such as client ID, client secret, token endpoint etc. and execute operations such as token exchange and token refreshing.
Our OAuth mediator cannot accomplish as it is designed only to communicate with the WSO2 IS and verify a set of given user credentials.
[1] - https://github.com/wso2/integration-studio-examples/tree/master/migration/mule/oauth2-authorization-code-using-the-http-connector