User identification in GitHub Applications #61617
Replies: 2 comments
-
Hey there! 👋 Thanks for posting in the GitHub Community, @yashodgayashan! We're happy you're here. You are more likely to get a useful response if you are posting your question in the applicable category. The Accessibility category is a place for our community to discuss and provide feedback on the digital accessibility of GitHub products. Digital accessibility means that GitHub tools, and technologies, are designed and developed so that people with disabilities can use them. I've gone ahead and moved this to the correct category for you. Good luck! |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hi,
We have a GitHub application where we allow users to authenticate their repositories via the application to our platform. We have a tenant-based platform where users can connect their repositories and do some operations. We are accessing the repository data via the GitHub application. Due to this user can connect to someone else's repository if that has been authorized with the GitHub application.
Do we have a mechanism to restrict this or are we following any pattern to overcome this issue?
Thank you
Beta Was this translation helpful? Give feedback.
All reactions