Documentation is seriously misleading and lacking information
See original GitHub issueFirst, I like auth0, I need auth0, but auth0 is making my life very difficult, the one reason I want to move to auth0 is to make life simpler and not have to maintain additional cruft.
THE BIG Q: Is there a stable documentation for stable api, for stable version ?
I am new to Auth0 but I find it extremely difficult to integrate, with too many unknowns.
Almost all resources on the web are revolving around v7.
Now, v8 is at what version ? What should people use ? What is the most stable API ? The one used in the documentation or 8.1.2
? The one used in documentation is 8.0.4
Can’t the documentation be in sync in the git libraries ?
For https://auth0.com/docs/libraries/auth0js - is this all the API documentation there is ?
This is what I would like to use, but look at how well it is documented:
You get nothing!
I am not alone
https://auth0.com/forum/t/getuserprofile-equivalent-in-auth0-js-v8/4916/5
Then this
From https://auth0.com/forum/t/getuserprofile-equivalent-in-auth0-js-v8/4916/6 - for v8
So basically, the login method is still in wip
Then another gem, silentAuth
- we know it exists, some people use it, not documented at all.
Moving forward, the webAuth.popup.loginWithCredentials
… documented but deprecated (nowhere mentioned)
I am almost giving up, I am unable to have a proper login working, without pop-ups or custom page re-directions … That redirect can be avoiding using an iframe
(and still keep SSO), but it is not documented at all … there is this legendary usePostMessage
option to communicate with the iframe
, but to apply to which method of authentication - the only mention of that arg is in renewAuth
… but I am not able to go past log-in … so how can I arrive at renew ?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:19
- Comments:7 (4 by maintainers)
Holy F&$%!!!
I just spent several evenings trying to get custom authentication working with my angular-cli (Angular 2) app. I had completely given up on Auth0 and was working on moving to Firebase, only to then discover the LoginComponent from your ‘Angular 2+ Custom Login’ is broken/incomplete.
Specifically, this button triggers a full page refresh which breaks authentication workflow
This should either be
type="button"
, or you should clearly point out the FormsModule from ‘@angular/forms’ needs to imported into the module containing the LoginComponent. YES, I should have spotted this error much sooner, but I took the example to be complete and spent a ton of time needlessly tracing auth0-js internals.It’s hardly worth mentioning given how frustrated I am about the form, but the ‘handleAuthentication’ function in the
Auth
class is also broken where it referencesauthResult.error
in theparseHash
callback. TheauthResult
object doesn’t have an error property; a separate error object is also passed into the callback function. I assume this should look something like the following:Hey there! I’m not sure what documentation you’ve been following, but everything that I have been working in has worked flawlessly. There were some snafu’s but I worked the kinks out for the most part.
Here is how I am authenticating my users. Firstly I have the user fill out my login.html form, which on clicking the submit button calls my onSubmit() function in login.component.ts. onSubmit().
onSubmit() then calls my auth.service.ts file, which is shown below:
I hope this helps, I haven’t had a single issue using Auth0 so far, and have found the documentation pretty straight forward - for the most part, with some confusing parts here or there depending on the version you’re using (v7 vs v8). After authentication gets called, my routes get unlocked by my auth.guard.ts, which I didn’t include, but can add it later if you want a reference on how to unlock the application, but they also cover this partially in their docs, though my implementation isn’t from Auth0.
All of the console.log messages are just for testing purposes for my sake. So I know where things are going wrong, and to ensure that everything is working properly. Take them out when you push the project into production.