- **status**: closed --> in-progress - **Comment**: I already merged this to master, but have realized now that this means if a user goes to /p/import_project/github they will be immediately sent to a GitHub auth page (unless they have already approved github oauth). I think we should revert this change, since that is not a good UX.
Perhaps we should consider having a server-side oauth token to use for these lookups where we don't want to force the user to authorize with github yet. --- ** [tickets:#7804] Use OAuth token for github project validation** **Status:** in-progress **Milestone:** unreleased **Labels:** 42cc github import **Created:** Tue Dec 02, 2014 06:59 AM UTC by Igor Bondarenko **Last Updated:** Tue Dec 02, 2014 04:53 PM UTC **Owner:** Igor Bondarenko Use OAuth token for project validation or else github will return 403 (probably only if request limit is reached) and user will see "This project is unavailable for import" message --- Sent from forge-allura.apache.org because [email protected] is subscribed to https://forge-allura.apache.org/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
