Case Study:Authorization issue when creating a Guest Collection on Globus
Open
Nobody has claimed this yet.
style: case study 🔎📝
system: data-mgmt 🗃️
- Dominant language
- Python
- Stars
- 24
- Forks
- 15
- Avg merge
- 10d 3h
- Merged PRs (30d)
- 1
Description
What would you like to see added?
When trying to create a guest collection on Globus, you may encounter an error message that looks like the below.
Steps that resolve this issue:
- When you encounter such error message , click on "Continue" to initiate the re-authentication process.
- The system will prompt you to log in again to authorize the missing scopes.
- After these two steps, you can check the Globus web app consent page. You will see "Manage collections on Cheaha cluster on-campus (UAB Science DMZ)" with other list of scopes for the case of 'on-campus Cheaha cluster".
See ticket number: RITM0777688
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No target file is named; first locate the repository's Globus or guest-collection documentation and review nearby case studies. Use the reported error, re-authentication steps, consent-page scope details, and RITM0777688 reference; done means the case study is published in the appropriate documentation location.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100