-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example code #1
Comments
You should use the master branch, as that is most like the final API. Those two methods being private is a bug indeed. I noticed it last weekend and fixed it locally, just didn't commit yet. I'm working on example code as well, but some changes to OAuthSession need to go in first. I hope to get that done next weekend. At this point, most wanted help is just using and testing and report and/or fix any bugs. |
Okey, Thanks :) |
The new oauth.webapp module is both a simple vibe.http.auth like API targeted towards web applications and a usage example of the underlying oauth.client API. |
Is there any chance that your module will be include in vibed? |
Doesn't seem very likely. Vibe.d documentation explicitly states that OAuth support should be provided by an extension library. Some vibe.d developers started their own, rejectedsoftware/user-auth, but that one seems to be abandoned. Anyway, I will make sure this library and vibe.d play well together. |
@Vild @bubnenkoff I opened a PR (#10) with an extracted example for using this great library to allow user login/signup via multiple OAuthProviders (Github, Google in my example) and saving them to a persistent storage (Mongo for simplicity). Maybe it's a bit helpful ;-) |
Hey, I need OAuth for one of my projects and it looks like this project would really fit me.
I see that the master branch differs a lot from the v0.0.1-alpha tag, so I'm wonder which I should use.
I would guess that the master branch isn't really done yet, because it
userAuthUri
anduserSession
are private. (Bug?)Is there anything I could help with?
The text was updated successfully, but these errors were encountered: