Skip to content
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

Is issue #833 back again? #22

Open
richb201 opened this issue Dec 26, 2020 · 7 comments
Open

Is issue #833 back again? #22

richb201 opened this issue Dec 26, 2020 · 7 comments
Assignees

Comments

@richb201
Copy link

richb201 commented Dec 26, 2020

I just added a third tenant and i am seeing this:
A 404 status code is returned from the Start Passwordless API when more than one tenant exists in FusionAuth.

This was solved in "Resolves GitHub Issue #833, thanks to @atrauzzi for reporting and helping us track this one down!"
This was reported solve din 1.19.0. I am using 1.19.7 and also experience this (it is repeatable). Can this be?

Please advise.

@robotdan
Copy link
Member

robotdan commented Dec 29, 2020

In general, you should use a tenantId on the request when you have more than one tenant. However, in most cases we can resolve the correct Tenant Id - the issue you mentioned (FusionAuth/fusionauth-issues#833) allows us to correctly resolve the Tenant from the applicationId on the request.

Can you confirm you are using the 1.19.7 version of the client and the FusionAuth server? Also, please provide an example JSON request that is causing a 404.

@robotdan robotdan reopened this Dec 29, 2020
@richb201
Copy link
Author

richb201 commented Dec 29, 2020 via email

@robotdan
Copy link
Member

The only reason 404 would be returned is if the applicationId of 2cf00c29-ac46-49bf-8cd4-32538ddb00d8 does not exist or is disabled, or if a user [email protected].

You can confirm the user exists, and the applicationId is correct, and ensure the loginId does not contain any trailing whitespace or other characters.

Does the issue go away if you provide a tenantId on the request?

@richb201
Copy link
Author

richb201 commented Dec 29, 2020 via email

@robotdan
Copy link
Member

I don't think your screenshot came through, you may want to comment directly on the issue, I think the email responses lose some things. #22

@richb201
Copy link
Author

richb201 commented Dec 30, 2020 via email

@richb201
Copy link
Author

richb201 commented Dec 30, 2020 via email

@robotdan robotdan self-assigned this Dec 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants