-
Notifications
You must be signed in to change notification settings - Fork 0
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
Adding support for SPAs #8
Comments
@azataiot I'll mull it over the week. Not sure what your ETA for this work is. What I'm thinking in your use case is that we need to reroute all the redirect urls properly. The provider tutorial SHOULD actually be enough, we just need to add some more custom configuration. I'd totally be willing to work on this, but it's not high on my priority list since I don't primarily use SPAs. If you'd like to start a PR or have any questions, I'm happy to consult and answer all questions as this is pretty important to people. Number one rule: don't use grant type password. If you're planning on making a PR, first create a test repository and we'll work there. Then we can start merging and setting up a PR for this repository. |
The redirect urls after login on the provider side is just you doing I'm actually more inclined to do this now since it's pretty interesting. For the sake of my time as well, please provide a repository that includes a provider with React/Vue.js that uses SimpleJWT for authentication. I don't need a template for the consumer, just one for the provider :) @azataiot That'd be greatly appreciated! Just trying to manage my time properly for side projects :D It should also include a register and login process. |
This is a nice start here!As you said, Currently, the problem I have is that I should start or clone a new sample frontend that is much more Universal, rather than too much connected to my company logic. As for my time, I will able to do all the above after I finishing the current site, or on the weekends. |
Just a simple form, nothing special, not much css, just basic input tags is good enough. There's no need to do the OAuth integration, just a basic SimpleJWT setup. Does that sound similar to your company logic? I'm also only going to be able to work on this on the weekend. But thanks a ton for setting it up! |
no, we have setup too many things on the front end side also, I will try to
just copy the parts about jwt and test so that they work independently.
On Mon, 12 Jul 2021 at 11:16 Andrew Chen Wang ***@***.***> wrote:
Just a simple form, nothing special, not much css, just basic input tags
is good enough. There's no need to do the OAuth integration, just a basic
SimpleJWT setup. Does that sound similar to your company logic?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB7FVQXWKJBJLDUNSTNQDGLTXJ3EFANCNFSM5AGCDA6A>
.
--
[image: photo]
*Yaakov Azat*
Biryol Inc. & KazNU
+7 7081962952 <+7%207081962952> | +86 13240156994 <+86%2013240156994> |
***@***.***
http://yaakovazat.com
Al-Farabi Kazakh National University
<http://facebook.com/yaakovazat> <http://us.linkedin.com/in/yaakovazat>
<http://twitter.com/yaakovazat> <http://github.com/yaakovazat>
<http://soundcloud.com/yaakovazat>
"Only as high as I reach can I grow, only as far as I seek can I go, only
as deep as I look can I see, only as much as I dream can I be." - Karen Ravn
|
@azataiot generally though, your login system is basically filling out a form on the frontend then sending that info by hitting the SimpleJWT endpoints to get the access and refresh token right? |
To my regret, it is not that simple. There are several systems sitting between them for security reasons . |
No description provided.
The text was updated successfully, but these errors were encountered: