en:navody:owncloud:oc_identity
Action unknown: indexoauthloginauthoauthloginauthoauthloginauthoauthloginauthoauthloginauth

Splitting of consolidated external identities in Perun

A manual how to split consolidated external identities in Perun used to be here. It contained many warnings advising users not to do it without proper consideration (and preferably, not to do it at all). Users didn't care. So the manual is simple now: kindly contact user support.

A user should ideally have a single identity in the Perun user management system. This Perun identity can be created using an external identity. An external identity is an identity from user's home organisation, LDAP, or other sources. One or more external identities can be connected to a single Perun user. E.g. Perun user A can have external identities from an employer (e.g. CESNET), a university, Google, Facebook and so on.

As we are legally allowed to provide our services to a restricted community (“academic community” is a reasonable approximation), our users have to prove that they belong to the community from time to time. They usually do so logging in using one of the external identities. It is most likely an identity supplied by a university where the user works and/or studies. Other connected identities can be used for logging into services on daily bases.

What Perun hath joined together, let not man put asunder. By using this procedure, you declare that you understand its consequences and complications that may arise with using e-infrastructure services in the future and you have responsibility for them. Requests to re-join identities separated without thinking will be responded with frowned eyebrows by the user support.
If you create multiple resources using separated accounts, it will be quite difficult to connect them together in the future. So think twice before proceeding. Then think twice more, please. It has consequences to all e-infrastructure services you use.
We suggest that users with multiple Perun identities follow strict culture when using them. We suggest using one of them solely for accessing the service it was separated for, the other for the rest of services. Keep in mind that you have to keep track of what identity is used where.
You have been warned. Don't deny it.

<!– This tutorial describes how to split consolidated identities. You might want to do it in case you need to use several independent ownCloud accounts. It may be useful in cases when you work for several academic institutions and your work is so distinct in each one of them that you prefer having dedicated accounts even in the e-infrastructure. Note that our general recommendation is to connect your identities as much as possible. Please consider well if splitting your accounts counterweights the hassle with more difficult service access. There is no reason to do this “just to get bigger quotas”, contact user support instead.

This procedure requires you to understand how user identities are handled in the CESNET e-infrastructure (it is described below).
Never perform this procedure without consulting the user support. We are not responsible for your using this to solve problems that do not require such dramatic measures.

A user should ideally have a single identity in the Perun user management system. This Perun identity can be created using an external identity. An external identity is an identity from user's home organisation, LDAP, or other sources. One or more external identities can be connected to a single Perun user. E.g. Perun user A can have external identities from an employer (e.g. CESNET), a university, Google, Facebook and so on.

As we are legally allowed to provide our services to a restricted community (“academic community” is a reasonable approximation), our users have to prove that they belong to the community from time to time. They usually do so logging in using one of the external identities. It is most likely an identity supplied by a university where the user works and/or studies. Other connected identities can be used for logging into services on daily bases.

In this howto, we show how to remove an external identity (disconnect it from current Perun user). The identity can than be used to create another Perun user, which will be considered a completely separated entity from the e-infrastructure point of view.

What Perun hath joined together, let not man put asunder. By using this procedure, you declare that you understand its consequences and complications that may arise with using e-infrastructure services in the future and you have responsibility for them. Requests to re-join identities separated without thinking will be responded with frowned eyebrows by the user support.
If you create multiple resources using separated accounts, it will be quite difficult to connect them together in the future. So think twice before proceeding. Then think twice more, please. It has consequences to all e-infrastructure services you use.
We suggest that users with multiple Perun identities follow strict culture when using them. We suggest using one of them solely for accessing the service it was separated for, the other for the rest of services. Keep in mind that you have to keep track of what identity is used where.
You have been warned. Don't deny it.

How to remove an external identity from a Perun user:

1. Please go to the page for user identities management.

2. Click on My Identities in the left menu.

3. Please select the identity for which you wish to use a separate ownCloud account. Then click on remove.

4. Confirmation of identity removal will appear.

5. Now you can go to ownCloud address https://owncloud.cesnet.cz and sign in using the separated (removed) identity.

The identity you have separated can be now used to create a new Perun user.

–>

Last modified:: 30.07.2018 15:32