This page only applies if you are in the UK Access Management federation and your organisation uses the Jisc Certificate service ()
Once registered with the certificate service your authorised users can sign in using the institutional login. This page will help you set up OpenAthens to enable that - for instructions about using the Sectigo Certificate Manager, see https://support.sectigo.com/Com_KnowledgeProductPage?c=Sectigo_Certificate_Manager_SCM.
As with other resources, we don't know anything about the internal workings of the certificate manager service and can only help you with setting up the attributes and related release policy we've been told it requires.
urn:oid:0.9.2342.19200300.100.1.3 (email address)
urn:oid:220.127.116.11 (first name)
urn:oid:18.104.22.168 (last name)
The good news is that you will already have data in at least three of the four fields (email, first and last names). You may already have data in a field you use for eduPersonPrincipalName, but at most you'll need to add something to use for it. The thing where they've got weird-looking attribute names is handled in the release section.
EduPersonPrincipalName (EPPN) is something that looks like an email address, but isn't one. Unfortunately the handy looking email address field is about the only thing we can't reuse for this. What you'll need is either an existing field that has something unique to the user in it, or to create a new one in the schema editor for this - the good news is that the field only needs to be populated for the authorised users of the certificate service.
The following assumes you need to create a new attribute to use for EPPN - if you have a field that isn't an email address you can use such as staff ID number you can move on to the release section
Now make sure there is data in that field for each authorised user of the certificate service. It can be firstname.lastname if you like, but anything that is different for each user (and does not contain an '@' character is ok).
The good news is that you may already have data some of the four fields as they include email, first and last names. You may need to add an attribute and a mapping for the other one. The thing where they've got weird attribute names is handled in the release section.
EduPersonPrincipalName is something that looks like an email address, but isn't one. Unfortunately the handy looking email address field is one of the things we can't reuse for this (can't use anything with an '@'). What you'll need is either an existing field that has something unique to the user in it, or to create a new one in the schema editor for this - the good news is that the field only needs to be populated for the authorised users of the certificate service.
As this needs to be released, you will have to set up any schema attributes before adding any mappings:
Repeat the above for any of the other attributes you don't already map to releasable attributes (the minimum other attribute in this case is email address). As they are likely to be used under different names for other services in the future, you may prefer to give them more generic target names such as email, firstname, and so on.
Next you will need to add mappings from your local source to the schema attributes as relevant (since only schema attributes can be releasable):
Repeat for any others that you need to map
As these are not attributes you want to send to everyone, you will need to add a resource specific policy:
You can test at