When using GoogleOpenIdOAuthProvider, the authorization / authentication flow for Google is the first time to authorize, but each time after that it is simply authenticated. For instance:
1) The application for the website goes to / auth / googleopenid 2) Google requests authorization of the application against the account, click "Accept" 3) Sent back to the application
If you log out and then go back to step (1), step (2) will be skipped, as you would expect.
Using TwitterAuthProvider step (2) - clicking the "Authorize application" button - happens every time. This makes twitter recording less convenient.
See an example with Servicestack's own demo:
http://bootstrapapi.apphb.com/
Other answers I found say that he should call Twitter "oauth / authenticate" and NOT "oauth / authorize".
So, is there a way to configure Servicestack to work this way, or is it just a mistake?
source share