I’ve recently implemented the new react spa sdk for my website. Everything works great but my Login and Signup button right now redirect to the same login form. What is the best practice for a “signup first” form in this new sdk? The wrapper has a “loginwithredirect” function but no “signupwithredirect”. Thanks!!
Are you using the New ULP (Universal Login Page) or the Classic one (the one with the login/signup tabs)?
In case it’s the New ULP: it’s currently not possible to directly jump to the signup page instead of the login page, but might available in the future. (I had asked this internally before about a month ago, because I had somebody asking me the same question, but at the moment it’s not possible. I added it to the product backlog though).
(It is possible wit the Classic login page though.)
@mathiasconradt thanks for the reply. Yes I am using the new ULP. Any idea when the feature will be implemented? (estimate is fine). Also how did you guys set up your sign up for the Auth0 website? Custom Sign Up with /dbconnections/signup API call? Thanks!
@mathiasconradt thanks for the pointers. how should I integrate signup for my single page react app with the auth0 spa client then? I like the new ULP a lot more and don’t really want to switch back. Is there also a way to know if the user is new or not?
@mathiasconradt i’m aware of the quickstart tutorial, I’ve already implemented auth0. I was asking, with the new auth0 spa react sdk how can you tell if a user just signed up for the first time or logged in? thanks
Why does this rule need ‘http://example.com’ to work and it can’t just be a normal key like ‘logins’?
As for why I’m trying to figure out if the user is new: if it is the user’s first time logging in i would like for them to be redirect to a different url (/signup) and go through a signup process.
This https://example.com is a custom namespace, that’s relevant if you want to use custom claims to add to an ID or access tokens.
Note this info and the reason behind it:
You can add custom claims, but they must conform to a namespaced format to avoid possible collisions with standard OIDC claims.
Any non-Auth0 HTTP or HTTPS URL can be used as a namespace identifier, and any number of namespaces can be used. The namespace URL does not have to point to an actual resource, it’s only used as an identifier and will not be called by Auth0.
I also want to directly call the Signup Page. In fact, many big sites always show the Sign Up page first and you have to always switch to Login Page. This is imho much better than the other way round and will probably have a better conversion rate.
Please, let us know, when you have implemented the possibility for a direct call to Signup, maybe with a parameter like mode: ‘signUp’ or so.