Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Custom resources, once created, can be allocated to permission sets just like any other resource. This is only necessary if you are using MyAthens though.

Add a new custom resource

From the custom tab of the resource catalogue you can add a resource record 

This page is about custom resources rather than custom SAML resources. A basic custom resource is essentially just a managed link that can appear in MyAthens and you can define the name, description and access URL. Why you might want or need to do this is discussed on the custom resources FAQ page.

If you are on the new authentication point at login.openathens.net the add button brings up a dialogue for resource type - either custom or SAML - otherwise you will only be able to create custom resources.

Custom resource

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 resourceThis kind of resource does not appear in reports because unless the access URL goes through our authentication point we don't see it happen.

Add a new custom resource

From the custom tab of the resource catalogue click the add button and select custom from the dialog.

Image Modified

The URL must include the protocol at the beginning - e.g. 'http://wwww...', 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.

...

These are identified in the catalogue with a 'Custom' tag:

Image Modified

SAML resource (login.openathens.net only)

These are used where you have the SAML 2 metadata of the target 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

Image Removed

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:

Image Removed

You will usually need to tell the other application about your own metadata or endpoints before it will - see the SAML 2 sections in:  how to access your own metadata.

SAML 1.x is not supported for this kind of connection.

Manage an existing custom resource

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:

Image Modified

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.

Extra options on SAML resources (login.openathens.net only)

Custom SAML resources have two attitional 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 nessisary.

Delete a custom resource

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.

Image Modified

 

 

Widget Connector
urlhttps://www.youtube.com/watch?v=FC-lAXMVWG0


 

Multimedia
name09 - Custom resources.mp4
width75%
pageDemonstration videos