No, if your service needs provisioning, you must arrange this yourself.
No. For more background information, see:
Whether a rich client supports federated login with one of the standards used by SURFconext (e.g. SAML or OpenID Connect) depends on the developer of that rich client. The support must be built into the rich client and often also on the server of the service. SURFconext cannot make the rich client compatible. SURFconext can advise institutions about services that have rich clients associated with them. We can also pressure vendors to support federations in their designs.
Inform SURFconext and provide us with the new metadata before you upload it to the Production environment. If you inform us in time, there will be no downtime for the users.
No. Use eduID for guest access.
SURFconext operates with a minimal disclosure principle: only the absolute necessary (personal) information is transferred to a service. When you, you must specify the attributes needed. We will review your request and configure an Attribute Release Policy accordingly.
See Use of single-tenant and multi-tenant services in SURFconext.
Yes. You can force users to authenticate when they log in. By setting
true, single sign-on is disabled. If the user already had a session with their IdP, that will be ignored.
Yes, you can create your own WAYF selection page.
Generally it is because the IdP did not release the required attribute. SURFconext operates with a minimal disclosure principle: only the absolute necessary (personal) information is transferred to a service.
Not from SURFconext: use your own logging.
Yes, via eduGAIN. Please refer to this documentation for more information.
SURFconext Teams offers an easy way to manage collaborative groups. The groups are organised centrally and can be used with cloud services. A group can be set up so that only the members of that group have access to restricted data on a particular cloud service (more information).
Currently only SAML2 and OpenID Connect are supported.
schacPersonalUniqueCode attribute. Note that only a very limited number of IdPs are providing this attribute. If you want to use/provide this attribute contact firstname.lastname@example.org.
Note that SAML logins always run via the user's browser, so it is not usually necessary to allow any direct connections between our systems and yours for the login process.
Our SP registration systems need to be able to fetch your SP's metadata though. For that, you can whitelist:
We check regularly if an SP is still being used. If no logins are recorded during some time (see below), we will remove the connection. Before doing so, we will notify the SP.
Currently, the timeout periods are defined as follows:
|Test connections||1 year||14 days|
Test connections must receive minimum 1 login within the first 6 months. Otherwise they will be removed.
Use the eduPersonEntitlement attribute:
To scope the entitlement values, we include the SP's principle domain in the value.
The SP "bookkeeper.example.org" needs the "FinanceRole" attribute, with possible values "user", "manager" and "administrator". In SURFconext, this can be passed on in an eduPersonEntitlement:
This is a bug introduced by Microsoft in an attempt to fix a security issue. The security issue (CVE-2019-1006) is described here: https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1006 In particular, the problem arises when using the following method for reading metadata: https://docs.microsoft.com/en-us/dotnet/api/system.identitymodel.metadata.metadataserializer.readmetadata?view=netframework-4.8
The patch that has been rolled out changes the way XML digital signatures are verified. It seems to “fix” things by ignoring all KeyInfo elements other than the first child of a Signature element, and expecting it to contain an X509Data element. We have spoken with the responsible Microsoft developers and they acknowledge that the implementation is faulty. However, until now they have not prioritized fixing this issue in .NET. It may be helpful to report that you are affected by this problem to Microsoft to give it more priority.
A workaround is to apply an XSLT transform to remove the first KeyValue element from the signed metadata file, for example like this: strip.xslt