Posts made by francis.ducharme

@francis-ducharme

Well, this one was simple. By scoping the API request to the target tenant I was able to do it.

if (tenantId != "")
                client.DefaultRequestHeaders.Add("X-FusionAuth-TenantId", tenantId);

Added this in the function in question.

Hi there,

I designed an Azure Function that allows for user creation/registration. The function demands that an email address and a FusionAuth application ID be provided, looks up if the user (email) already exists as registered for that application, then creates it if not.

Problem is that the Azure Function in question talks to FusionAuth with a specific tenant ID, application ID, client secret, client ID, etc.

It thus cannot go peer into another tenant's data (users). If I try to create a user by providing a FusionAuth application ID that's not within the configured tenant of the Azure Function, FusionAuth says the application ID does not exist.

Is there a way to do operations with the API across all tenants configured in our FusionAuth instance ?

Thanks.

Hi there!

Is there any way in the login process to have custom parameters received in the defined callback method ?

As you can see, I am redirecting the user's browser to a static URL, but I'd like this URL to be dynamic, depending on custom parameters received when Google (the identity provider in this case) calls my Callback method

Is this possible ?

@dan said in Wrong logout URL being returned ?:

@francis-ducharme What is your setting for logoutBehavior for each application config? All applications or redirect only?

By default it is 'all applications' which means that FusionAuth, on logout, will call each application's logout url (to ensure that the user is logged out of all applications). It does this via an iframe, so I'd expect both to be requested. https://fusionauth.io/docs/v1/tech/guides/single-sign-on#configure-the-applications-in-fusionauth has a bit more.

I'm not sure why you are ending up at localhost for the dev app, though.

That was it. All my application's logout behavior were set to "All Applications". "Redirect" only made it so the browser doesn't get redirected to "localhost".

Thanks!

@dan said in Wrong logout URL being returned ?:

@francis-ducharme Hi Francis,

Is this still an issue? I'd review your application configuration (in the 'Applications' tab) to double check that the logout url is correct there.

Also, it'd be helpful to know the version of FusionAuth you are running.

Hi Dan! I have upgraded to the latest version and this is still an issue. It seems the logout URL being returned is being confused between different versions of the app (localhost, dev, staging, etc).

@dan said in Wrong logout URL being returned ?:

@francis-ducharme Hi Francis,

Is this still an issue? I'd review your application configuration (in the 'Applications' tab) to double check that the logout url is correct there.

Also, it'd be helpful to know the version of FusionAuth you are running.

Hi Dan! Sorry for the delay in responding. Everything seems fine on my end

This is the config for my "Dev" version of the application

As you see, I'm supposed to be redirected to an URL on the internet, but here's what I see in Chrome network tab

"localhost" is what I have in the Logout URL for the "local" version of the app (what the devs use when developing locally on their PC)

We use version 1.32.0.

Thanks!

I have this problem when logging out my users from my application that I'm being returned the wrong logout URL by FusionAuth.

I've got two applications configured in FusionAuth. One for "localhost" (for local development) and one "DEV" for our development environment, which is hosted in the cloud.

The logout url for the "localhost" version of the FusionAuth application is something like: https://localhost:4455/api/FusionAuth/logout

And the DEV one is the same but hosted in the cloud, https://exampledomain.com/api/FusionAuth/logout

When users click "Logout" in my app, there are taken to: ourserver.fusionauth.io/oauth2/logout?client_id=the_client_id

When logging out when locally running the app, the client ends up redirected to the DEV logout url (in the cloud) and when logging out from the DEV instance of our application, the client ends up redirected on "localhost".

It's the inverse of what I expect. I'm sure I use the correct client_id/secret in both instances so I'm a little confused.

Any ideas ?