This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| encryptedpat [2025/07/02 16:22] – admin | encryptedpat [2025/07/02 16:57] (current) – admin | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ======Using an Encrypted PAT====== | ======Using an Encrypted PAT====== | ||
| - | This note is only for // | + | This note is only for // |
| The encrypted PAT that a manager receives from an owner can be used to create a repository or add/remove repository members. (Read about [[/ | The encrypted PAT that a manager receives from an owner can be used to create a repository or add/remove repository members. (Read about [[/ | ||
| Line 10: | Line 10: | ||
| When it asks for the Encrypted PAT; at that point, the manager should paste in the encrypted key that was obtained from the owner. | When it asks for the Encrypted PAT; at that point, the manager should paste in the encrypted key that was obtained from the owner. | ||
| + | |||
| + | **Troubleshooting**\\ | ||
| + | |||
| + | - If the encrypted PAT is not working, it usually means that the owner of the PAT erroneously may have given the actual PAT (which should never be done, frankly) In this case, request the owner to create an encrypted version of the PAT as explained in this help. | ||
| + | - Even with the correct encrypted PAT, it is possible that adding and removing members may not be possible. That is because //only managers// of a repository (and of course the owner) can do that work. So ask the owner, to make you the manager of the repository you want to add/remove members. | ||
| ---- | ---- | ||
| [[concepts? | [[concepts? | ||