indigo-iam / iam-website Goto Github PK

Included in IAM PR #637

See task https://issues.infn.it/jira/browse/INDIAM-145

Basically, the conclusion of what has been discussed here with some screenshot, merged into this documentation.

Basically, go trough those properties.

I am looking into deploying the IAM service, and wanted to look into Docker for flexibility.
The documentation page points to a configuration reference, but the link is dead:

See the configuration reference for a description of the variables.

Would be good to have minimal instructions, even though it is quite simple...

Document how account linking can be disabled in the IAM system administrator guide

PR indigo-iam/iam#668

Linked to this PR indigo-iam/iam#499

@giacomini suggests to start from this google doc.

We can add client-registration configuration properties in the Configuration section.
Basically, it should be an explanation of those properties.

Reference: https://indigo-iam.github.io/v/v1.8.2/docs/reference/api/proxycert-api/

Related to indigo-iam/iam#630

Minor oddity: for consistency it would be good to always use the same extension when referring to keystore files. Depending on pages, currently varies between .jks and .jwks.

In newer DB versions, the existing example:

GRANT ALL PRIVILEGES on iam_test_db.* to 'iam_test'@'%' identified by 'some_super_secure_password';

No longer works. Instead, one must now use:

CREATE USER 'iam_test'@'%' identified by 'some_super_secure_password';
GRANT ALL PRIVILEGES on iam_test_db.* to 'iam_test'@'%';

This renders the current documentation out of date.

Consider Admin, Group Manager and User.

We should specify here that the top level IAM group has to be equal to the VO name. Top level groups different from the VO name will not appear in the proxy.

Related to IAM issue 590, specify also the allowed VO names.

In particular, add information on client modification using RAT

Some link targets are defined using relative URLs rather than absolute ones but the site URL doesn't resolve to the appropriate location, meaning that these links are broken.

e.g. lifecycle.timestamp, lifecycle.status or cern_person_id, and so on..