Angular, Auth0, and Netlify are a perfect combination for creating, securing, and deploying your application.
Brought to you by #GuestAuth0r @pjlamb12
Angular, Auth0, and Netlify are a perfect combination for creating, securing, and deploying your application.
Brought to you by #GuestAuth0r @pjlamb12
Let us know folks if you have any questions!
Thanks for reading! Are there any other parts of the application that could or should be secured after deploying to Netlify?
@pjlamb12 this tutorial is erroring out on the hosted url shared https://pjlamb12-ng-auth0.netlify.com/ and is the same case after noth localhost and netlify builds being run.
@konrad.sopala Please help resolve this error in your kickstart tutorial for Angular + Auth + Netlify
@konrad.sopala resolved it with the logs feature technical errors section. Thanks
It seems that the redirect_uri that you have in your code isn’t added to the allowed callback urls. You need to go to the dashboard and to your application and add that here:
@konrad.sopala now I am getting the Failed Exchange Error after successful SignUp and Login for the user. As per Success Login and a Failed Exchange - #5 by sagun786 I have updated the “implicit” Grant Type also
Here are the Errors from Logs
In terms of details of the Error attaching the Log
{
“date”: “2020-08-13T08:12:55.226Z”,
“type”: “feacft”,
“description”: “Unauthorized”,
“connection_id”: “”,
“client_id”: “gNkJFP7YEvD4OrBdbgjHYZzM8XwkhjYS”,
“client_name”: null,
“ip”: “116.86.21.67”,
“user_agent”: “Safari 13.1.0 / Mac OS X 10.15.4”,
“details”: {
“code”: “*************4s5”
},
“hostname”: “vanna.au.auth0.com”,
“user_id”: “”,
“user_name”: “”,
“log_id”: “90020200813081256620000465921382865527023048504050188338”,
“_id”: “90020200813081256620000465921382865527023048504050188338”,
“isMobile”: false
}
Please refer this related ticket raised by another member on a separate thread
This has been fixed. Netlify changed from .com to .app, so I just had to update the callback URLs. Sorry about that!
No worries! Glad you have it eventually working!
Thank you for your reply, Preston
@pjlamb12 Should we go ahead and update the blog post?