| Info |
|---|
Login using OAuth2.0 is available since MediaHaven version 18.4. It is the preferred way of authenticating for new integrations. |
...
Company name / publisher
Name of your integration
Description of your integration
Destination server(s)
Redirect-URL(s)
If providing multiple redirect-uri(s), you will need to provide the correct one when making requests to the authentication portal
After we review your application, you will be sent a client_id and a client_secret which you can then use in the OAuth2.0 flow.
...
2. Obtaining a token
Client Credentials Grant a.k.a. interactive flow.
| Info |
|---|
If your app offers a UI, you are required to use this flow |
Redirect user to the MediaHaven
...
Authentication Portal
Let's assume we want to connect to https://integration.mediahaven.com. For your actual connections, change the URL accordingly.
...
If the user clicks the "Authorize" option he will be redirected back to your initially registered Redirect-URL, with the Authorization code as query parameter:
https://demo-app.com/redirect?code=OORO1gjyWP7Mr9ztl2Dvp06NjR2kTApc
If you have multiple redirect_uri’s registered, you need to supply the correct one using the redirect_uri query parameter.
| Tip |
|---|
Redirect-URL are strictly matched. You can however add a |
...