MCP Management Portal - User Guide

To update the contact information of your organization, click the "Update" button on the "My Organization" page.

Make the changes and click "Update organization".

You can change the logo of your organization. The logo is only used in the list of organizations, which every user of the MCP Management Portal can see. Should no logo be uploaded, a default logo will be displayed.

To upload a new logo, click on the logo on the "My Organization" page and browse to the new logo.

Not yet implemented.

Not yet implemented.

To create a Vessel or Device, click the "+" in the list.

Fill out the form and click "Register Device/Vessel". The "Permissions" field is explained in depth in the Permissions section of this guide.

To create a Vessel or Device, choose it in the list and click the "Update" button on the details page.

Make the changes and click "Update device".

Warning: If you delete an entity, all issued certificates will be revoked and become invalid.

To delete click the "Delete" button on the entity you want to delete.

If an organization is federated into MCP, you do not need to create users!
The users will automatically be created the first time they log in on a webpage that uses MCP, such as the MCP Management Portal.

If an organization is not federated into MCP and is using the "ProjectTestUsers" Identity Provider, users must be created manually in the Management Portal. When the user has been created, he/she will receive an email with instructions for how to log in with a temporary password.

When an organization is federated into MCP, users are automatically created and updated when they log in on a webpage that uses MCP, such as the MC Management Portal.

In the case that an organization is not federated into MCP, but is using the "ProjectTestUsers" Identity Provider, users must be updated manually in the Management Portal.
Updating the password of a user cannot be done in the portal, this must be done from the "ProjectTestUsers" Identity Provider.

For organizations, which is federated into MCP, users are automatically created or updated when they log in on a webpage that uses MCP, such as the MCP Management Portal. Therefore, deleting users does not make much sense for federated organizations, unless it is necessary to clean up the user list, or to remove all the users’ certificates.

If an organization is not federated into MCP and is using the "ProjectTestUsers" Identity Provider, users can be deleted from the portal. This will also remove the user from the "ProjectTestUsers" Identity Provider. The user will no longer be able to log in to access MCP services.

When a user is deleted all of the user’s certificates are revoked.

In the certificate, there are several information’s about the entity. Please refer to the online documentation.

On every entity details page, there is a certificate section. This section is the same component for all entities. Therefore, the description and examples applies for all.

To issue a new certificate, click on the "Issue new Certificate" button.

Click on "Issue Certificate".

And that is it. A certificate has been issued and is ready for download.

When you download you will receive a zip file that contains public key, private key and certificate in PEM format, and the certificate in .p12 and .jks keystores. The password for the keystores are written in a .txt file that is also contained in the zip file.

NOTE: It is very important that you download the certificate, because it is the only time, that you can download the public- and private key.

When a certificate needs to be revoked, find the relevant user/vessel/device/service and the certificate that should be revoked at click on "Revoke".

This will show a window where you will have to choose a reason and a date for the revocation in the selectors. Once these has been entered you can click "Revoke".

The certificate will now have been revoked and the certificate will be marked as such in the certificate list.

To view a Specification, click "Specifications" in the menu and a list of specifications appear. Click on any column of a row in the list to view that Specification.

In the details page, you can see a subset of the Specification data. To view all data, you can download the actual documents that were uploaded upon the registration of the Specification.

To register a new Specification, click "Specifications" in the menu and a list of specifications appear. Click the "Register new Specification" button at the bottom of the list.

Now you can upload 2 documents (see online documentation for templates of the documents):

When the XML-file is uploaded, there will be a validation of the Specification ID, which should be a MRN (refer to the MRN - Maritime Resource Name section of this guide. An example MRN for DMA would be: urn:mrn:mcl:service:specification:dma:nw-nm

When all is uploaded correctly, click the "Register Specification" button.

Not yet implemented.

Not yet implemented.

To view a Technical Design, click "Designs" in the menu and a list of Technical Designs appear. Click on any column of a row in the list to view that Design.

You can also get to the design by clicking any column of a row if you have a Specification in view.

In the details page, you can see a subset of the Technical Design data. To view all data, you can download the actual documents that were uploaded upon the registration of the Technical Design.

To register a new Technical Design, you need to select the Specification you want the Technical Design to implement. When the Specification is selected, you should click on the "Register new Design" at the Specification details page.

Now you can upload 2 documents (see online documentation for templates of the documents):

When the XML-file is uploaded, there will be a validation of the Technical Design ID, which should be a MRN (refer to the MRN - Maritime Resource Name section of this guide. An example MRN for DMA would be: urn:mrn:mcl:service:design:dma:nw-nm

When all is uploaded correctly, click the "Register Design" button.

Not yet implemented.

Not yet implemented.

To view an Instance, click "Instances" in the menu and a list of Instances appear. Click on any column of a row in the list to view that Instance.

You can also get to the Instance by clicking any column of a row if you have a Technical Design in view.

In the details page, you can see a subset of the Instance data. To view all data, you can download the actual documents that were uploaded upon the registration of the Instance.

To register a new Instance, you need to select the Technical Design you want the Instance to implement. When the Technical Design is selected, you should click on the "Register new Instance" at the Technical Design details page.

Now you can upload 2 documents (see online documentation for templates of the documents):

When the XML-file is uploaded, there will be a validation of the Instance ID, which should be a MRN (refer to the MRN - Maritime Resource Name section of this guide. An example MRN for DMA would be: urn:mrn:mcl:service:instance:dma:nw-nm

When all is uploaded correctly, you can provide additional information to the service if you should need to issue certificates for the service later. This includes the field "Certificate Domain Name", where you should enter the name of the domain where the service will be hosted (e.g. Service.dma.dk) and the field "Permissions" which will also be embedded in the certificate. Should this not be relevant for your service, simply leave the fields empty.

When everything is OK, click the "Register Instance" button.

Not yet implemented

Not yet implemented.