Hi, when I invite a new user, the user gets the "Setup password" email.

When they click the link, they get the following error:

{
"error" : "invalid_request",
"error_description" : "The request is missing a required parameter: redirect_uri",
"error_reason" : "missing_redirect_uri"
}

The URL does have the client_id in it, however. Shouldn't FusionAuth be able to set the correct request_uri from the client/application configuration?

Thanks,

Nick

Hi, when I invite a new user, the user gets the "Setup password" email.

When they click the link, they get the following error:

{
"error" : "invalid_request",
"error_description" : "The request is missing a required parameter: redirect_uri",
"error_reason" : "missing_redirect_uri"
}

The URL does have the client_id in it, however. Shouldn't FusionAuth be able to set the correct request_uri from the client/application configuration?

Thanks,

Nick

Hey Dan,

We want to have different configurations for each customer, because each customer may have e.g. a different SAML provider.

Therefore, we decided to create one application for internal-admins, and one application for each customer.

Does that make sense?

Also, what is the benefit of segmenting by group, in addition to segmenting by application?

Thanks,

Nick

Hello,

I'm trying to understand how FusionAuth would work best for a SaaS app with two kinds of accounts: customers and internal admins.

The internal company logins are e.g. sales people, developers, customer services, etc. They need to be able to access an internal admin portal, and in addition, a sandbox customer account for testing.

It seems like it could be convenient to let internal admins share one user account and an app-switcher to toggle between their admin-view and their customer-view.

Is it a best practice? Is it unsafe in any way?

Thanks,