Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
en:metadata_admin_tool [2023/10/05 14:20] – Wolfgang Pempeen:metadata_admin_tool [2024/02/21 11:32] (current) – Wolfgang Pempe
Line 22: Line 22:
 Please note that we added a new role called "subadmin" (as of 11/9/2022). Metadata admins can invite subadmins independently and delegate the administration of metadata of individual IdPs/SPs to them. (See below for details.) Please note that we added a new role called "subadmin" (as of 11/9/2022). Metadata admins can invite subadmins independently and delegate the administration of metadata of individual IdPs/SPs to them. (See below for details.)
  
-==== How to get your initial credentials for the new tool ==== +==== How to get your initial credentials for the MD Admin Tool ==== 
-Your old credentials will not work in the new metadata admin tool (released Nov. 9th). You will receive an invitation link to the e-mail address you registered with. Follow the link in the e-mail. It only works once, though. If you followed the link earlier but did not set a password, please use the password reset link.+You will receive an invitation link to the e-mail address you registered with. Follow the link in the e-mail. It only works once, though. If you followed the link earlier but did not set a password, please use the password reset link.
  
 ==== Two factor authentication ==== ==== Two factor authentication ====
Line 47: Line 47:
  
  
-==== New role: Subadmin ====+==== Further role: Subadmin ====
 In the new metadata administration tool the role of subadmins is a new feature. It enables regular metadata admins to delegate the administration of metadata of individual IdPs/SPs to third parties. They do not have to involve DFN-AAI hotline into account creation for subadmins. (Regular metadata admins with full access still have to be registered via the hotline though.) In the new metadata administration tool the role of subadmins is a new feature. It enables regular metadata admins to delegate the administration of metadata of individual IdPs/SPs to third parties. They do not have to involve DFN-AAI hotline into account creation for subadmins. (Regular metadata admins with full access still have to be registered via the hotline though.)
  
Line 127: Line 127:
   * Select a file from your local computer and choose a meaningful name for the list.   * Select a file from your local computer and choose a meaningful name for the list.
   * If your file does not comply with the image size that can be displayed in the common UI interfaces, you can let our server scale it for you by ticking "Autoscale". The metadata administration tool does not accept any logos or favicons that are too big or too small. Thus, if you do not enable autoscaling you have to make sure the images have the correct size.{{:en:metadata_admin_tool:logos-en.png?600 |}}   * If your file does not comply with the image size that can be displayed in the common UI interfaces, you can let our server scale it for you by ticking "Autoscale". The metadata administration tool does not accept any logos or favicons that are too big or too small. Thus, if you do not enable autoscaling you have to make sure the images have the correct size.{{:en:metadata_admin_tool:logos-en.png?600 |}}
- 
-===== Main differences between old and new MD admin tool ===== 
-^ old ^ new ^ 
-| password login only | **2FA** is mandatory | 
-| self-signed certificate had to be verified by the hotline | **Self-signed certificates** can be used without hotline interaction | 
-| All metadata admins had write access to everything in the organization's account. | Metadata admins can add **subadmins** and delegate certain metadata entries to them. | 
-| Logos/Favicons were published in the metadata as external URLs. It was possible to link to images with unsuitable sizes. | (New) **Logos/Favicons** are uploaded to the tool and delivered by it. Files are scaled to the right size during the upload. | 
-| New entities could be added by fetching xml metadata from a remote URL. | Existing **xml metadata files** can be uploaded. | 
-| Scopes were entered in the IdP metadata form. | **Scopes** are regarded as meta information that is maintained on the level of the organization. They can then be assigned to individual IdPs. | 
- 
  
  • Last modified: 8 weeks ago