...
When setting up an SSO between Mediahaven and the customer, the SSO will ensure that:
A new user is automatically created in Mediahaven (if the user logs on for the first time and does not yet exist) with the default rights as configured.
The IdP is used for authentication. When a user navigates to MediaHaven, the authentication request will be sent to the IdP of the customer. In this respect, if the user is not authorized, he/she will also not be able to login in MediaHaven.
Info |
---|
Based on the information above, it is important that a new user always first authenticates in MediaHaven using the SSO. This way, the user account will automatically be created. In no case should a MediaHaven account be created manually by an admin user. |
Once the user account is created in MediaHaven, a MediaHaven administrative user can update rights and permissions for that particular new user account.
Note |
---|
Important: in
|
Required information to setup the SSO
Information supplied to the customer (IdP)
todo
Information needed for Zeticon (SP)
todoIn order to allow MediaHaven to connect to your IdP, the only information needed is/are the application callback URL(s) that will be used:
https://$HOSTNAME/simplesaml/module.php/saml/sp/saml2-acs.php/$ORGANISATION_NAME
https://$HOSTNAME-QA/simplesaml/module.php/saml/sp/saml2-acs.php/$ORGANISATION_NAME
Information to be provided to Zeticon
In order for us being able to configure the SSO in MediaHaven, following information needs to be provided:
Link to the Federation Metadata
Test account (username/password) so we can verify the correctness of the SSO after installation
App registration Client ID
Who to contact in case of technical issues on your side
Federation Metadata URL | |
Test account *username/password) | |
https://docs.seon.io/knowledge-base/user-manuals/sso-integration#connect-your-sso-account-with-seon
...