CollaboratorAccount: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
= | =What is it?= | ||
UMIACS provides a | UMIACS provides a special account type that can facilitate collaboration with non-UMIACS Faculty, Staff and Employees. These accounts can access resources such as our [[GitLab]] source code and project management tool, our [[OBJbox | ObjectStore]] , Wikis, and other web-based applications. These accounts do not have any storage and any access to [[GitLab]] repositories, [[OBJbox | ObjectStore]] buckets, etc. fall under their account sponsor and/or the PI. We also have a new more flexible Security Group that will replace our UMIACS Application Resources. The new Security Groups are managed in our [https://intranet.umiacs.umd.edu/directory/groups/ UMIACS Directory Application]. | ||
==How do I create a Collaborator Account?== | ==How do I create a Collaborator Account?== | ||
| Line 8: | Line 8: | ||
==How do you reset a Collaborator Account password?== | ==How do you reset a Collaborator Account password?== | ||
This is done by the account sponsor through the Collaborator account list in the [https://intranet.umiacs.umd.edu/requests/accounts/collaborators UMIACS Requests Application]. The account sponsor will generate a token and send email to the Collaborator with a link to reset their password. | This is done by the account sponsor through the Collaborator account list in the [https://intranet.umiacs.umd.edu/requests/accounts/collaborators UMIACS Requests Application]. The account sponsor will generate a token and send email to the Collaborator with a link to reset their password. | ||
==What is the difference between a UMIACS Application Resource account and the new UMIACS Collaborator Account?== | ==What is the difference between a UMIACS Application Resource account and the new UMIACS Collaborator Account?== | ||
UMIACS Application Resource accounts are being deprecated in favor of the new UMIACS Collaborator Account. Each Application Resource will need all its accounts converted and the applications reconfigured to use the new Security Group framework. Staff will work with our AR owners to make this transition. | UMIACS Application Resource accounts are being deprecated in favor of the new UMIACS Collaborator Account. Each Application Resource will need all its accounts converted and the applications reconfigured to use the new Security Group framework. Staff will work with our AR owners to make this transition. | ||
Revision as of 17:14, 9 January 2018
What is it?
UMIACS provides a special account type that can facilitate collaboration with non-UMIACS Faculty, Staff and Employees. These accounts can access resources such as our GitLab source code and project management tool, our ObjectStore , Wikis, and other web-based applications. These accounts do not have any storage and any access to GitLab repositories, ObjectStore buckets, etc. fall under their account sponsor and/or the PI. We also have a new more flexible Security Group that will replace our UMIACS Application Resources. The new Security Groups are managed in our UMIACS Directory Application.
How do I create a Collaborator Account?
A UMIACS Account holder has to sponsor the Collaborator Account. This is done in our UMIACS Requests Application. This will generate a token and send email to the Collaborator to set their details (including a username and password). Once the Collaborator has created the account a email will be sent to the account sponsor, staff and Collaborator that the account is ready to use.
How do you reset a Collaborator Account password?
This is done by the account sponsor through the Collaborator account list in the UMIACS Requests Application. The account sponsor will generate a token and send email to the Collaborator with a link to reset their password.
What is the difference between a UMIACS Application Resource account and the new UMIACS Collaborator Account?
UMIACS Application Resource accounts are being deprecated in favor of the new UMIACS Collaborator Account. Each Application Resource will need all its accounts converted and the applications reconfigured to use the new Security Group framework. Staff will work with our AR owners to make this transition.