In the Mura admin create a webservice and set it to OAuth2 Password and then use it's client_id and client_secret with this
You can choose to keep the client_secret an actual secret or not. It just depends on if you care if it's wide open or not.
This flow does not expose any sensitive data because JS in the client can't hide secrets
- Redirect to login
{web_login}?response_type=token&client_id={client_id}&redirect_uri={redirect_uri}&state={state}
User logs in and is redirected to {redirect_uri}?token_type=bearer&expires_in={expires_in}&access_token={access_token}&state={state}
- Redirect to login
{web_login}?response_type=code&client_id={client_id}&redirect_uri={redirect_uri}&state={state}
-
User logs in and is redirected to {redirect_uri}?code={code}&state={state}
-
Get access_token with code