Custom Identity provider errors
See original GitHub issueWe’ve been using the Custom Identity provider up until now and it’s been working great. Today it seems like it has stopped working.
const session = await ConnectyCube.createSession({ login: email, password: token });
produces the following:
{"code": 404, "info": {"errors": ["User not found"]}}
We’re not seeing any errors from our API (endpoint which the custom identity uses). As I said, everything has been working OK up until now so I don’t think it’s on our end although I will not rule it out. Has anything changed on your end? Or something not working quite right?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
Troubleshooting identity provider issues - TechDocs
This problem can happen if: User is not added to the custom IdP provider. IdP provider fails to complete the sign in process....
Read more >Custom external identity provider login error
Error when trying to click with custom external login provider.
Read more >Specify an error page for Identity Provider, SAML, or SSO
Use a custom error page: This setting redirects users to the fully qualified URL of your custom error page. This option is useful...
Read more >Working with custom identity providers - AWS Transfer Family
Describe the use of custom identity providers. Custom identity providers use an API Gateway.
Read more >Use the Identity Provider Event Log - Salesforce Help
When you're using Salesforce as an identity provider, use the identity provider event log to see information about login attempts. For example, see...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We are on the way of investigation. The root cause is identified, the patch is on the way
It’s working for us as well. Thanks!