1. Home
  2. Categories

Categories

  • Announcements regarding our community

    Release
    92
    Topics
    139
    Posts

    danD

    If you go look at https://fusionauth.io/docs/ and scroll to the bottom, you'll see a new section called 'Download docs'.

    Screenshot 2025-05-19 at 9.19.23 AM.png

    This takes you to fusionauth.io/docs/llms-full.txt which is all of our documentation (5MB!) in one file so you can upload it to your favorite LLM and query it.

    Hope you all find it useful.

  • Connect with other community members to discuss CIAM, architecture, app development, and more.

    576
    Topics
    1.9k
    Posts

    mark.robustelliM

    @michaelginn529 What do you have your "Logout behavior" set to for the application? Any other specific configuration you can share would help as well.

  • Share your tips and feedback with FusionAuth and the FusionAuth community.

    87
    Topics
    287
    Posts

    danD

    FYI, this was fixed in 1.60.0, per the release notes.

    In version 1.59.0 the password is now optional when creating or updating a user.

    When returning from a third-party login, a user may be prompted to complete registration by entering a password when self-service is enabled and is configured to require a password.

    This was unintended and has been corrected.

    https://fusionauth.io/docs/release-notes/

    Tracking issue: https://github.com/FusionAuth/fusionauth-issues/issues/3159

  • You've got questions? We've got answers.

    1.6k
    Topics
    5.0k
    Posts

    R

    Hello everyone,

    We’re trying to retrieve the event.info.deviceDescription field from the user.login.success webhook event, but it doesn’t seem to appear in the payload.

    Here’s an example of what we receive:

    "event": { "applicationId": "af28e0b2-124b-4c98-b8b5-30322e98de79", "authenticationType": "PASSWORD", "connectorId": "e3306678-a53a-4964-9040-1c96f36dda72", "createInstant": 1759824184881, "id": "c3e5c82a-91cc-451c-9bcc-104803d29f87", "info": { "deviceName": "macOS Chrome", "deviceType": "BROWSER", "ipAddress": "192.168.65.1", "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36" }, "ipAddress": "192.168.65.1", "linkedObjectId": "69384417-206b-4c21-a4e7-22f8c93ed516", "tenantId": "68530993-d5d0-43c5-9278-115524701723", "type": "user.login.success", "user": { "active": true, "connectorId": "e3306678-a53a-4964-9040-1c96f36dda72", "data": { ... }, "email": "XXXX", "id": "69384417-206b-4c21-a4e7-22f8c93ed516", "identities": [ { "insertInstant": 1759295385386, "lastLoginInstant": 1759761531077, "lastUpdateInstant": 1759295385386, "primary": true, "type": "email", "value": "XXXXX", "verified": false, "verifiedReason": "Trusted" }, { "insertInstant": 1759295385386, "lastLoginInstant": 1759824184881, "lastUpdateInstant": 1759295385386, "primary": true, "type": "phoneNumber", "value": "XXXXXX", "verified": false, "verifiedReason": "Trusted" } ], "insertInstant": 1759295385386, "lastLoginInstant": 1759824184881, "lastUpdateInstant": 1759295385386, "memberships": [], "passwordChangeRequired": false, "passwordLastUpdateInstant": 1759295385391, "phoneNumber": "XXXXXX", "preferredLanguages": [], "registrations": [ { "applicationId": "af28e0b2-124b-4c98-b8b5-30322e98de79", "data": {}, "id": "d57496f5-98de-4e36-9aa0-01b7b56fca50", "insertInstant": 1759295385398, "lastLoginInstant": 1759824184881, "lastUpdateInstant": 1759295385398, "preferredLanguages": [], "roles": [], "tokens": {}, "usernameStatus": "ACTIVE", "verified": true, "verifiedInstant": 1759295385398 } ], "tenantId": "68530993-d5d0-43c5-9278-115524701723", "twoFactor": { "methods": [ { "id": "SGN8", "lastUsed": true, "method": "sms", "mobilePhone": "XXXXXX" } ], "recoveryCodes": [] }, "usernameStatus": "ACTIVE", "verified": true, "verifiedInstant": 1759295385386 } }

    I tried setting metaData.device.description in the authorize request, like so:

    GET /oauth2/authorize?...&metaData.device.description=MyDescription

    But the description still doesn’t appear in the event payload.

    Am I missing a configuration step, or is deviceDescription not included in this webhook by default?

    Thanks in advance for any help!

  • Share and discuss community blog posts.

    169
    Topics
    190
    Posts

  • A read-only knowledge base of questions asked and answered about FusionAuth.

    111
    Topics
    229
    Posts

    danD

    Just an FYI, as of 1.59.0, phone number verification is now fully supported in FusionAuth.

    Read more here: https://fusionauth.io/docs/lifecycle/manage-users/verification/gate-accounts-until-user-phone-verified

  • Connect with people who can help you with FusionAuth projects.

    13
    Topics
    15
    Posts