Logo_WHITE.png

Frog Education

Frog Integration | SSO-Configuration

SAML 2 Name Comments

Entity ID


A URL in a domain that you own that can be used to uniquely identify the application. Case sensitive.

This is only used as an identifier - it doesn't have to really exist as a web page.

 

Development environments need a distinct Realm/Entity ID from their live counterparts. Choose your Realm/Entity ID for each environment early and stick with it.

 

Examples:
https://live..com/ (live environment)
https://dev..com/ (dev environment)
 


Assertion Consumer Service (ACS)


The URL in your app that the SSO token should be posted to. Often case sensitive.

For your live app, this must be https (not http).

This will be a specific page defined by your SAML implementation
(look for the <AssertionConsumerService> element in your metadata where the Binding attribute is - "urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
and copy the Location attribute).

 

Examples:

Live, SimpleSAMLphp:
https://www.myfrogapp.com/saml/module.php/saml/sp/saml2-acs.php/default-sp

Dev, SimpleSAMLphp:
http://localhost:12345/saml/module.php/saml/sp/saml2-acs.php/default-sp

 


Other pages in this section...

#
With Single Sign-On (SSO), users benefit from a single centralised repository service that federates individual school instances of FrogLearn. For more information about Entity ID / Realm, have a look at our SSO configuration reference page.
#
To implement Single Sign-On, your app will need a dedicated FrogLearn landing page. This will be the URL that your app within FrogLearn redirects to.

Supporting Information

#
When adding your app to the Frog federated IdP, the following data is needed at registration time.
#
With Single Sign-On (SSO), users benefit from a single centralised repository service that federates individual school instances of FrogLearn.

Switch Section