Open dazzaji opened 8 years ago
For Google, using the "login" only scope, we would expect to have the following words (or something really close and that links to the actual words they actually clicked on) in the account screen for the user when the auth for Google is active:
"iAuth would like to:
View your email address
View your basic profile info
By clicking Allow, you allow this app and Google to use your information in accordance with their respective terms of service and privacy policies. You can change this and other Account Permissions at any time."
Using example app "Calendly" when app card from full list is clicked, it expands to show:
Notice that "Authorization date: October 3, 2015" is displayed at bottom of the card.
Remove access Are you sure you want to remove access? Calendly will no longer have access to your Google Account. You'll need to grant access if you want to use the app or site again.
Clicking "edit" shows options for more specific authorizations, in this case, selecting specific "circles" NPR app is authorized to access.
jekyll-auth
Step 15: Open a browser and navigate to the Heroku URL https://my-new-cool-herokuapp.herokuapp.com. You should be automatically redirected to a GitHub page asking for authorization: Authorize application - my-new-cool-new-heroku-app by @foo-organization/foo-team - would like permission to access your account. You can click on Authorize application.
IAuth currently uses this for login:
Public data only Limited access to your public data. This application will be able to identify you and read public information. this is what the test says.
This will be a matter of using design elements like material design or maybe bootstrap and having re-usable clauses in a template that we dynamically update for each user to by in sync with the authorizations they current have active. Some clauses between the user and UnWorkshop account service (like the liability and venue) may be the same no matter how many or few authorizations a user currently has active.