Wolfram Single Sign-On Site License Configuration

Single sign-on (SSO) is currently available to organizations with an Unlimited Site license with open, campuswide access. At present, Wolfram supports SAML2 SSO protocols. If your organization has a different type of site license or is using a different authentication protocol, contact us.

After completing the form, you will receive an email confirmation containing the information you have provided, along with the link to Wolfram's metadata.

Customer Information

Name *

First name *Last name *

First name *

Last name *

Email address *

Organization *

Wolfram site license number(s) *

Wolfram product(s) *

Additional email addresses

Please enter any additional email aliases or email addresses for all individuals who should be included in conversations to set up SSO at your organization.

Authentication Basics

Is your campus part of a school system where individual campuses share the same authentication mechanism?

No Yes

What identity provider do you use?

How are your users going to access Wolfram products?

IDP Server Metadata

Please provide the URL to access your IDP server metadata or upload the XML file.

URL *-or-Upload XML file *

URL *-or-

Upload XML file *

If your metadata requires validation, please provide the URL to access the additional certificate or upload the certification file.
A Base64-encoded certificate is preferred.

URL -or-Upload certificate

URL -or-

Upload certificate

Comments

User Properties Returned and Their Descriptions

Please provide the properties that will be passed for each user who will be authenticated through SSO. This information is needed to properly map user information to our database.

* Required in order for the handshake to work with our system. The additional properties are optional, but passing that information to us will give you better data on your users.

"Friendly" field name*Key*Notes

Unique immutable user identifier *

e.g. remoteUserId

e.g. urn:oid:0.9.2342.19200300.100.1.1

Email address *

e.g. emailAddress

First name *

e.g. firstName

Last name *

e.g. lastName

User affiliation *

e.g. userAffiliation or PrimaryAffiliationUser

Will pass multiple values (separated by commas)

Department

Major

Expected graduation date

Current degree track

Comments

User Affiliation Mapping

Authorized User Affiliations

Please use this section to provide the following information:

Step 1: Enter each of the authorized user affiliations that should be provisioned access, which will be passed to our system. The user affiliation is the data in your system that classifies the type of user, such as faculty or student. If you will be passing more than five authorized affiliations, please include them in the comments.

Step 2: Select a mapping value for each of your authorized user affiliations. All affiliations must be mapped to one of these values: Faculty or Student. It is standard for all site licenses to cover faculty, staff and students. Alumni no longer qualify as students, but emeritus faculty can qualify as faculty if allowed by the organization. If affiliation mapping is not set up on our end, users will not be provisioned access to the site license.

Step 3: If your system passes multiple affiliations for a single user, indicate the mapping priority. Some users may have multiple affiliations (e.g. student and employee). If multiple affiliations are passed for a single user, our system will choose the mapping value with the highest priority for that user (where 1 is the highest priority). If your system passes only a single affiliation for each user, you may skip this step.

For your convenience, we have pre-filled this section with example user affiliations and suggested mapping values and priorities. Please update the associated mapping values and priorities if your user affiliations don't match those provided.

Enter your user affiliationsChoose mapping valueChoose mapping priorityBelow are some examples of how the mapping priority will affect the mapping value (which affects how access is provisioned) in situations where multiple affiliations are passed for a single user.

student (1) + employee (4) = student → Student → Provisioned
alumni (non-authorized) + faculty (2) = faculty → Faculty → Provisioned
faculty (2) + member (non-authorized) = faculty → Faculty → Provisioned
alumni (non-authorized) + emeritus (5) = emeritus → Faculty → Provisioned
alumni (non-authorized) + member (non-authorized) = non-authorized → Not Provisioned𝑖

Comments

Non-authorized User Affiliations

Please use this section to provide a comma-separated list of user affiliations that should not be provisioned access to products through your site license. If multiple affiliations are passed for a single user, as long as one of the values is an authorized user affiliation, they will be provisioned access.

Email Domain(s)

Please provide a comma-separated list of all email domains that should be enabled for single sign-on. This will be used to set up domain autodetection on our sign-in page, which can autotrigger SSO. All subdomains will be automatically enabled unless explicitly excluded under the "Restricted subdomain(s)" section below.

NOTE: we will only enable this after everything has been configured and tested.

Restricted Subdomain(s)

Alumni are not covered by your site license agreement. Please specify any subdomain + domain combinations that are issued exclusively to alumni.

Commercial or government-funded research labs, institutes or university affiliates whose primary mission is not the direct teaching of students or academic research are not covered by your site license agreement. Please specify any subdomain + domain combinations that are issued exclusively to members of these organizations.

SSO Integration Rollout

Please provide us with a preferred date for rolling out SSO integration to your users. This can be synced with the renewal of your site license, completed during a break or scheduled whenever is best for your campus. We will do our best to accommodate your request.

I have read and agree to Wolfram's Privacy Policy.

If you are a human, leave me blank