Is there a way to check what browsers are being used by our tenant users? We want to see XYZ tenant, how many users are using E.G Chrome, Safari, ...

@tkates
I was thinking you had created a SAML v2 identity provider in FusionAuth which has a reconcile lambda.

Now, I understand that FusionAuth is configured as a SAML v2 IdP where FusionAuth is the system of record for the users. Thus, the application is setup as a SAML application using the SAML tab for the application which has the Populate Lambda.

Since that Lambda is for populating the SAML response, an option would be to use the Lambda HTTP Connect to update the user inside the populate lambda.

@mike-rudat

I wanted to confirm that the generic messenger does not have re-try logic built-in on a failure.

@mike-rudat

Yes, I verified using the SAML V2 and PagerDuty Integration. From the documentation, copy the Login URL from the FusionAuth SAML v2 Integration details section and paste it in PagerDuty’s own Login URL field and append the idp_hint query string parameter for an external IdP. In turn, the user was taken directly to the IdP login screen.

Can a SAML application login request with an idp_hint query string parameter send the user directly to an IdP login screen?

Does the generic messenger have re-try logic built-in on failure? I see that webhooks support re-try logic.

Hi @tkates,

The SAML v2 Populate Lambda is used to add additional values to the SAML response.

If you want to update the user and/or registration, then use the SAML v2 Reconcile Lambda.

Let me know if this helps.

Thank You,

Mike

Hi Mike,

I ran a test where 4000 url's were added to:

System Settings->CORS->Allowed origins

I used the

/api/system-configuration

API to add the url's. Note, the page itself now takes a significant time to load as 4000 url strings are being rendered.

Cheers

Currently, we have around 2000 IdP's. Will FusionAuth be able to add 2000 urls in the allowed origins field? Does that field have any size limit?

Hi Mike,

You could add a logoutLink at the end of the template inside the end of helpers.main to logout and then redirect the user back to the registration page such as:

     <div class="form-row push-top">
       [@helpers.logoutLink  redirectURI="${request.contextPath}/oauth2/register"]${theme.message("register")}[/@helpers.logoutLink]
     </div>
  [/@helpers.main]

The template would display for example with the link titled register at the bottom of the page in the attached screenshot.

Cheers

If I enter the wrong email address during registration, how can I re-register when on the Verify Registration Required template. That template is a dead end page for the user.

This is an application where

Verify registrations is set

Thank You