You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A website needs to implement this interface IAuthenticationCallbackProvider. This allows the developer to handle the callback from the Provider (eg. Google).
eg. Once the user auth's against Google, we come back to our website .. and then what?
i) do we create a new user?
ii) update the details on an existing user?
iii) do we need to ask for more credentials?
iv) did the user reject the permissions request (ie. no Google, don't give out my email).
Ok - so the developer now needs to handle this. Fine.
So i've exposed to interfaces which I believe handle most scenarios.
a) Process
b) OnRedirectToAuthenticationProviderError
Now, with the process .. i'm assuming that MOST of the time the code will be grabbing the user info from the provider and then storing that in the db. Because of this database-assumption I'm wondering
if the method Process should be renamed to ProcessAsync and it returns a Task<dynamic>? Assumption here is a db requirement is async. The con to this is that I'm now making assumptions of the developers and it's very possible that they will NOT do any db/I-O bound stuff.
For the method OnRedirectToAuthenticationProviderError this is gerenally just a redirect to their own error page. But there is no reason why this method also can't do something I-O bound, like send a logging error to LogEntries or RayGun, etc.
If I leave them as notasync, then how would a person do something async in one of those methods if they needed to storea user record asyncly, for example?
The text was updated successfully, but these errors were encountered:
- Referencing the NancyFX MyGet library for the latest -pre which includes updates to the INancyModule interface.
- Added a NuGet.config file to reference the MyGet api.
- Removed the ICache (fixesSimpleAuthentication#145).
- Removed the HttpClient code. Now uses the WorldDomination.HttpClient.Helpers package instead.
- Provider key is not required to be sent to the Provider. The session now stores this.
- IAuthenticationProviderCallback returns dynamic (closesSimpleAuthentication#155).
- IAuthenticationProviderCallback methods are not async (closesSimpleAuthentication#151).
A website needs to implement this interface
IAuthenticationCallbackProvider
. This allows the developer to handle the callback from the Provider (eg. Google).eg. Once the user auth's against Google, we come back to our website .. and then what?
i) do we create a new user?
ii) update the details on an existing user?
iii) do we need to ask for more credentials?
iv) did the user reject the permissions request (ie. no Google, don't give out my email).
Ok - so the developer now needs to handle this. Fine.
So i've exposed to interfaces which I believe handle most scenarios.
a)
Process
b)
OnRedirectToAuthenticationProviderError
Now, with the process .. i'm assuming that MOST of the time the code will be grabbing the user info from the provider and then storing that in the db. Because of this database-assumption I'm wondering
Process
should be renamed toProcessAsync
and it returns aTask<dynamic>
? Assumption here is a db requirement is async. The con to this is that I'm now making assumptions of the developers and it's very possible that they will NOT do any db/I-O bound stuff.OnRedirectToAuthenticationProviderError
this is gerenally just a redirect to their own error page. But there is no reason why this method also can't do something I-O bound, like send a logging error to LogEntries or RayGun, etc.If I leave them as not
async
, then how would a person do something async in one of those methods if they needed to storea user record asyncly, for example?The text was updated successfully, but these errors were encountered: