Page History
...
This usually applies only to internal connections such as your VLE, but can also come up for things like Adobe's Creative Cloud enterprise or Google Apps's G Suite.
If the resource or app has published metadata, you can add it in the same way as any federation metadata via the administration console. If their metadata is not published, you must manually add it to the runtime, which is usually a job for your IT team.
...
If they do not let you upload metadata, the things they might ask for include:
Item | Means | Use |
---|---|---|
SSO address | Where your users should be sent to log in | E.g. https://idp.yourdomain.com/oala/sso Can be looked up on the overview tab |
Logout address | Where you users should be sent to log out | E.g. https://idp.yourdomain.com/oala/logout Can be looked up on the overview tab |
Upload a signing certificate | The x509 certificate that would normally be read from your metadata | If they ask for this you will need to copy and paste some data from your metadata into a text file - see below |
Specify SAML version | Use the one that came out in 2005 (SAML 2) or the older one. | SAML 2 |
Redirect or POST |
Redirect |
How to copy your certificate from your metadata
...