Topics created by mike.rudat

@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.

@mike-rudat

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

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

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.

Screenshot 2024-05-02 at 23.54.08.png

Cheers

WarpStream is a Apache Kafka compatible data streaming platform. The Kafka Integration in FusionAuth can be used to integrate WarpStream with FusionAuth.

In the configuration, set bootstrap.servers to the WarpStream agent port such as localhost:9092. This is the port the Agent will listen on for Kafka client TCP connections.

Thanks for the question.

FusionAuth allows you to create a custom theme. In this custom theme, you can add JavaScript (JS) that might offer you the analytics you are looking for. For instance, you could add Google Analytics or a similar JS engine to collect this metadata information.

Another option is that you can use webhooks to listen for login events (or related events). Most webhook events will include a field of:

event.info.userAgent [String] AVAILABLE SINCE 1.30.0 The user agent associated with the event.

Which might return data like

"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36"

You could collect and analyze this data to get a better understanding of how your users are interacting with FusionAuth.

Lastly, we do store some metadata on the refresh tokens (if you use our hosted login pages), which might be helpful for information-gathering purposes by Tenant.

"metaData": { "device": { "description": "Hooli Phone 8GB Work Phone", "lastAccessedAddress": "170.152.81.62", "lastAccessedInstant": 1487996477628, "name": "Richard's Hooli Phone", "type": "MOBILE" },

https://fusionauth.io/docs/v1/tech/apis/jwt#retrieve-refresh-tokens

Let us know if we can provide you with anything else.

@mike-rudat This might be of interest too: https://fusionauth.io/docs/extend/examples/device-limiting