Path to function: Resources > Catalogue > Custom
Custom resources, once created, can be allocated to permission sets like any other resource.
From the custom tab of the resource catalogue you can add a resource record. Why you might want or need to is discussed on the custom resources FAQ page.
The add button brings up a dialogue for resource type - either custom or SAML:
This is essentially just a managed link that can appear in MyAthens and you can define the name, description and access URL for the custom resource.
The URL must include the protocol at the beginning - e.g. 'http://...', and could also be a mailto: link or any other kind of web protocol. Titles are limited to 100 characters, descriptions to 255 and URLs to 512.
Information links and categories are optional but if present can be used to present additional information to your users.
These are identified in the catalogue with a 'Custom' tag:
These are used where you have the SAML 2 metadata of a target that is not in a federation such as your VLE, or Google Apps. This should not be used where a resource exists in federation metadata.
You are first asked for the resource's metadata and you can supply the URL or upload a file
This creates the resource immediately. You may need to edit some settings for name or logo and this is done as described in the managing an existing custom resource section below.
These are identified in the catalogue with a 'SAML' tag:
You will almost always need to tell the other application about your own metadata or endpoints before it will work - see the SAML 2 sections in:
From the custom tab of the resource catalogue, click on the name of the resource you want to modify. This will access nearly the same options as when modifying any other type of resource with one additional option - you can choose to make the resource available to your sub-organisations so that they do not have to set it up themselves:
On the visibility tab there is the option to allow the resource to appear in the 'All' tab of your sub-organisations' catalogues. The cascade to default permission sets option when used on a custom resource will automatically update this setting if it needs to.
Unlike regular resources, sub-organisations cannot modify a custom resource that you have made visible to them. They can however create their own custom resources if they need to.
Custom SAML resources have two additional tabs which allow you to upload a second certificate or update the metadata.
Updating the metadata will overwrite any customisations you have made to other fields so should be done only when necessary.
From the catalogue, click on the resource title to bring up its details page and click on the trash button next to the save button.