From 37c7344b682b03ba3bbac28290fe664e279c703e Mon Sep 17 00:00:00 2001 From: Alex Patterson Date: Tue, 8 Oct 2024 16:19:28 -0400 Subject: [PATCH 01/13] 441 --- astro/src/components/api/API.astro | 136 +++++++++++------- .../multi-factor-authentication.mdx | 5 +- .../content/docs/sdks/_static-patch-note.mdx | 36 ++--- 3 files changed, 94 insertions(+), 83 deletions(-) diff --git a/astro/src/components/api/API.astro b/astro/src/components/api/API.astro index 2df1958ea9..1cc639afd6 100644 --- a/astro/src/components/api/API.astro +++ b/astro/src/components/api/API.astro @@ -1,11 +1,18 @@ --- import APIAuthenticationIcon from "src/components/api/APIAuthenticationIcon.astro"; -import Aside from "src/components/Aside.astro"; +import StaticPatchNote from "src/content/docs/sdks/_static-patch-note.mdx"; interface Props { - authentication?: ['api-key' | 'basic' | 'client-credentials' | 'jwt' | 'local-bypass' | 'none']; + authentication?: [ + | "api-key" + | "basic" + | "client-credentials" + | "jwt" + | "local-bypass" + | "none", + ]; description?: string; - method: 'GET' | 'POST' | 'PUT' | 'PATCH' | 'DELETE'; + method: "GET" | "POST" | "PUT" | "PATCH" | "DELETE"; showPatch?: false; title?: string; uri?: string; @@ -14,7 +21,7 @@ interface Props { const { authentication, method, showPatch, title, uri }: Props = Astro.props; // Parse URI -let parts= []; +let parts = []; let parameters = null; if (uri) { @@ -24,90 +31,113 @@ if (uri) { let q = uri.indexOf("?"); if (q >= 0) { parameters = uri.substring(q); - url = url.substring(0, q ); + url = url.substring(0, q); } // Optionally extract one or more segment. - let type = 'literal'; - let atom = ''; + let type = "literal"; + let atom = ""; for (let i = 0; i < url.length; i++) { let c = url.charAt(i); atom += c; - if (c === '{') { + if (c === "{") { if (atom.length > 0) { - parts.push({type: 'literal', value: atom.substring(0, atom.length - 1)}); + parts.push({ + type: "literal", + value: atom.substring(0, atom.length - 1), + }); } - type = 'segment'; - atom = '{'; - } else if (c === '}') { - parts.push({type: 'segment', value: atom}); - type = 'literal'; - atom = ''; + type = "segment"; + atom = "{"; + } else if (c === "}") { + parts.push({ type: "segment", value: atom }); + type = "literal"; + atom = ""; } } if (atom.length > 0) { - parts.push({type: 'literal', value: atom}); + parts.push({ type: "literal", value: atom }); } // Account for a literal URL w/out any parameter segments if (parts.length === 0) { - parts.push({type: 'literal', value: url}); + parts.push({ type: "literal", value: url }); } } const authenticationTypes = { - 'api-key': '/docs/apis/authentication#api-key-authentication', - 'none': '/docs/apis/authentication#no-authentication-required', - 'jwt': '/docs/apis/authentication#jwt-authentication', - 'basic': '/docs/apis/authentication#basic-authentication-using-an-api-key', - 'client-credentials': '/docs/apis/authentication#client-credentials', - 'local-bypass': '/docs/apis/authentication#localhost-authentication-bypass' -} + "api-key": "/docs/apis/authentication#api-key-authentication", + none: "/docs/apis/authentication#no-authentication-required", + jwt: "/docs/apis/authentication#jwt-authentication", + basic: "/docs/apis/authentication#basic-authentication-using-an-api-key", + "client-credentials": "/docs/apis/authentication#client-credentials", + "local-bypass": "/docs/apis/authentication#localhost-authentication-bypass", +}; --- -{(authentication || title) && -
- { authentication && -
- { authentication.map(auth => - - - +{ + (authentication || title) && ( +
+ {authentication && ( +
+ {authentication.map((auth) => ( + + + + ))} +
+ )} + {title && ( + + {title} + )}
- } - { title && - { title } - } -
+ ) }
- { method } + {method} - { uri && - parts.map(part => - { part.value } - ) - + { + uri && + parts.map((part) => ( + + {part.value} + + )) }{ parameters && { parameters } } + -->{ + parameters && ( + + {parameters} + + ) + }
-{ showPatch && method == 'PUT' && -
- - -
+{ + showPatch && method == "PUT" && ( +
+ + +
+ ) } - diff --git a/astro/src/content/docs/lifecycle/authenticate-users/multi-factor-authentication.mdx b/astro/src/content/docs/lifecycle/authenticate-users/multi-factor-authentication.mdx index 8a670b7746..e315677a7b 100644 --- a/astro/src/content/docs/lifecycle/authenticate-users/multi-factor-authentication.mdx +++ b/astro/src/content/docs/lifecycle/authenticate-users/multi-factor-authentication.mdx @@ -16,6 +16,7 @@ import MfaMigration from 'src/content/docs/lifecycle/authenticate-users/_mfa-mig import MfaTroubleshooting from 'src/content/docs/lifecycle/authenticate-users/_mfa-troubleshooting.mdx'; import StepUpDiagram from 'src/diagrams/docs/lifecycle/authenticate-users/step-up-auth.astro'; import { YouTube } from '@astro-community/astro-embed-youtube'; +import StaticPatchNote from 'src/content/docs/sdks/_static-patch-note.mdx'; @@ -427,8 +428,8 @@ user_two_factor_removed=`echo $user| jq 'del(.[].twoFactor[])' -` curl -XPUT -H 'Content-type: application/json' -H "Authorization: $API_KEY" 'https://sandbox.fusionauth.io/api/user/00000000-0000-0000-0000-000000000004' -d "$user_two_factor_removed" ``` -The reason you need to retrieve the user and modify the data, then use `PUT` to update it, is because of how `PATCH` handles arrays. -[Read this tracking issue for more info.](https://github.com/FusionAuth/fusionauth-issues/issues/441) +{/* TODO: check if this still makes sense */} + ### Building Your Own Interface diff --git a/astro/src/content/docs/sdks/_static-patch-note.mdx b/astro/src/content/docs/sdks/_static-patch-note.mdx index 82c212ce86..f7b78ba64b 100644 --- a/astro/src/content/docs/sdks/_static-patch-note.mdx +++ b/astro/src/content/docs/sdks/_static-patch-note.mdx @@ -1,30 +1,10 @@ import Aside from 'src/components/Aside.astro'; - - -`PATCH` requests are handled differently than you might expect. `PATCH` operations allow you to modify only parts of an object in FusionAuth. - -In client libraries with static typing, such as this one for {props.client_library_language}, there are no strongly typed objects set as part of a `PATCH` request. Instead, a hash, dictionary or map object is used. Ensure that you are using multi level dictionaries that create JSON with nested keys, otherwise the `PATCH` request will fail. This allows use of key value pairs to build a `PATCH` request. - -For example, if you want to change only the name of an application using `PATCH`, you would want the JSON that is sent across the wire to look like this: - -```json title="Example PATCH Application JSON" -{ - "application": { - "name": "hooli-bought-us" - } -} -``` - -If you built a typed application request object and then serialized it, it would contain empty arrays or other default values. This would modify the object you were changing in ways you didn't expect. This would likely cause the system behave in ways you don't want. - -By requiring you to build nested key value pairs, the JSON serialization works correctly. This is essentially a limitation of the current implementation in {props.client_library_language} and FusionAuth `PATCH` support. - -For this behavior to work correctly with typed objects, FusionAuth would need to ensure the domain object had no default values, and then instruct the serializer to omit empty objects, empty arrays and other values from the resulting JSON. This would ensure that the `PATCH` was performed correctly with no unwanted side effects. - -Once support for [RFC 7396](https://github.com/FusionAuth/fusionauth-issues/issues/441) lands in FusionAuth, there may be some additional options for configuring a JSON serializer to allow use of typed domain objects for `PATCH`. - -An alternative that allows you to use typed objects immediately is to perform a retrieve operation, modify the object in memory, and then execute an update operation. These are functionally equivalent to a single `PATCH` operation. - +{/* +TODO: Does this make sense to update fully to allowing PATCH in this way? +*/} + + \ No newline at end of file From a58101f6fd0aec2e16f625a5e0de7bfbd7477018 Mon Sep 17 00:00:00 2001 From: Alex Patterson Date: Tue, 8 Oct 2024 16:19:41 -0400 Subject: [PATCH 02/13] 171 --- .../docs/lifecycle/authenticate-users/single-sign-on.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/astro/src/content/docs/lifecycle/authenticate-users/single-sign-on.mdx b/astro/src/content/docs/lifecycle/authenticate-users/single-sign-on.mdx index ea33aacaf3..de20a60bd1 100644 --- a/astro/src/content/docs/lifecycle/authenticate-users/single-sign-on.mdx +++ b/astro/src/content/docs/lifecycle/authenticate-users/single-sign-on.mdx @@ -15,7 +15,7 @@ import SessionsExpiration from 'src/content/docs/lifecycle/authenticate-users/_s import SSOLogin from 'src/diagrams/docs/lifecycle/authenticate-users/sso-login.astro'; import SSOLogout from 'src/diagrams/docs/lifecycle/authenticate-users/sso-logout.astro'; import { YouTube } from '@astro-community/astro-embed-youtube'; -import {RemoteCode} from '@fusionauth/astro-components'; +import { RemoteCode } from '@fusionauth/astro-components'; This guide will walk you through setting up single sign-on (SSO) between two web applications using FusionAuth as their common authentication and authorization server. You will use the hosted login pages for your login form. @@ -376,5 +376,5 @@ Navigate to Applications -> Your Application -> OAuth a * You can view the [example application's codebase](https://github.com/fusionauth/fusionauth-example-node-sso). * The [Tenant API](/docs/apis/tenants) can be used to manage single sign-on related configuration. -* This guide uses the hosted login pages. If you are using the Login API and building your own pages, [check out the comments on this issue](https://github.com/FusionAuth/fusionauth-issues/issues/171) for guidance. +* This guide uses the hosted login pages. If you are using the Login API and building your own pages, [see our Login API Overview](/docs/lifecycle/authenticate-users/login-api/) for guidance. * The [Logout and Sessions Guide](/docs/lifecycle/authenticate-users/logout-session-management) has more information about session management options beyond using the built in SSO session. From e353151db814eb018531e522ad2ad1f98fd69166 Mon Sep 17 00:00:00 2001 From: Alex Patterson Date: Tue, 8 Oct 2024 16:19:55 -0400 Subject: [PATCH 03/13] 275 --- .../content/docs/lifecycle/authenticate-users/oauth/modes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/astro/src/content/docs/lifecycle/authenticate-users/oauth/modes.mdx b/astro/src/content/docs/lifecycle/authenticate-users/oauth/modes.mdx index b05672c1ae..9bbcf02e40 100644 --- a/astro/src/content/docs/lifecycle/authenticate-users/oauth/modes.mdx +++ b/astro/src/content/docs/lifecycle/authenticate-users/oauth/modes.mdx @@ -214,7 +214,7 @@ The **First-party service authorization** mode is the inverse of the **Third-par With this mode, your OAuth server might display a "permission grant screen" to the user asking if they want to grant the third-party application permissions to your APIs. This isn't strictly necessary and depends on your requirements, but if it is, you want custom scopes. -Custom scopes are not currently supported in FusionAuth; here's the [GitHub tracking issue](https://github.com/FusionAuth/fusionauth-issues/issues/275). +Custom scopes are now supported in FusionAuth; you can find more information within [OAuth Scopes](/docs/get-started/core-concepts/scopes). ## Machine-to-machine Authorization From edb831deeadc3b854e15d8de5454e2a0f1cd1f54 Mon Sep 17 00:00:00 2001 From: Alex Patterson Date: Tue, 8 Oct 2024 16:20:08 -0400 Subject: [PATCH 04/13] 494 --- .../content/docs/lifecycle/migrate-users/general-migration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/astro/src/content/docs/lifecycle/migrate-users/general-migration.mdx b/astro/src/content/docs/lifecycle/migrate-users/general-migration.mdx index 9e44ccaed0..b4e1752c3c 100644 --- a/astro/src/content/docs/lifecycle/migrate-users/general-migration.mdx +++ b/astro/src/content/docs/lifecycle/migrate-users/general-migration.mdx @@ -501,7 +501,7 @@ FA_HOST=... curl -H "Authorization: $API_KEY" $FA_HOST'/api/user/search?queryString=data.migrated%3Atrue%0A' ``` -This will return all the users who've been migrated as well as a count, subject to the limits of FusionAuth's Elasticsearch integration. See this [GitHub issue](https://github.com/FusionAuth/fusionauth-issues/issues/494) for more on those limits. Here's an example of the output: +This will return all the users who've been migrated as well as a count, subject to the limits of FusionAuth's Elasticsearch integration. See [Maximum Users Returned Workarounds](https://fusionauth.io/docs/get-started/core-concepts/limitations#maximum-users-returned-workarounds) for how to get more from search. Here's an example of the output: ```json title="Results of the FusionAuth migrated user query" {"total":629,"users": [ ... ] } From 879fd6f80bd46547111aa0a5158cf850b72eb9b6 Mon Sep 17 00:00:00 2001 From: Alex Patterson Date: Tue, 8 Oct 2024 16:20:16 -0400 Subject: [PATCH 05/13] 77 --- .../docs/lifecycle/migrate-users/provider-specific/auth0.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/astro/src/content/docs/lifecycle/migrate-users/provider-specific/auth0.mdx b/astro/src/content/docs/lifecycle/migrate-users/provider-specific/auth0.mdx index d51b02ec9d..8fc4805c97 100644 --- a/astro/src/content/docs/lifecycle/migrate-users/provider-specific/auth0.mdx +++ b/astro/src/content/docs/lifecycle/migrate-users/provider-specific/auth0.mdx @@ -326,7 +326,7 @@ If your user uses TOTP for MFA, where they provide a one time code provided by a If your users use a different method unsupported by FusionAuth, then you should map the Auth0 method to a FusionAuth method. -* WebAuthn: [Follow this issue to see the status of FusionAuth WebAuthn support](https://github.com/FusionAuth/fusionauth-issues/issues/77). +* WebAuthn: [Authentication With WebAuthN & Passkeys](/docs/lifecycle/authenticate-users/passwordless/webauthn-passkeys). * Push Notifications: It is possible a [Generic Messenger](/docs/customize/email-and-messages/generic-messenger) would work, but this would require some investigation and custom coding. * Voice: A [Generic Messenger](/docs/customize/email-and-messages/generic-messenger) integrated with a solution like [Twilio Voice](https://www.twilio.com/docs/voice) should work. * Cisco Duo: A [Generic Messenger](/docs/customize/email-and-messages/generic-messenger) integrated with a solution like [Twilio Voice](https://www.twilio.com/docs/voice) could work. From df1c7fc778ef2cf8cd12b33b4fcb104cef479e0b Mon Sep 17 00:00:00 2001 From: Alex Patterson Date: Thu, 10 Oct 2024 13:38:16 -0400 Subject: [PATCH 06/13] 1319 --- .../manage-users/verification/_common-questions-gating.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/astro/src/content/docs/lifecycle/manage-users/verification/_common-questions-gating.mdx b/astro/src/content/docs/lifecycle/manage-users/verification/_common-questions-gating.mdx index c45a2be66d..7f6515fec7 100644 --- a/astro/src/content/docs/lifecycle/manage-users/verification/_common-questions-gating.mdx +++ b/astro/src/content/docs/lifecycle/manage-users/verification/_common-questions-gating.mdx @@ -7,9 +7,9 @@ To double-check your users, click on Users -> Search Bar and us **Question**: What if I have accidentally/inadvertently imported users with a `verified: false` value (either on the user or application registration)? In other words, can I do this manually. -**Answer**: Currently, there is no way to change this value manually. However, there is an open issue adding this functionality. Please upvote if you believe this is needed. +**Answer**: Currently, there is no way to change this in the Admin UI. However, there is an [open issue](https://github.com/FusionAuth/fusionauth-issues/issues/2897) adding this functionality. Please upvote if you believe this is needed. -https://github.com/FusionAuth/fusionauth-issues/issues/1319 +You can currently set `user.verified` within the [user API](/docs/apis/users). **Question**: What does it mean to enable both registration and email gates and verification paths? From 8b150cac8ef9638e659c4af0adcbf4f72f43abd6 Mon Sep 17 00:00:00 2001 From: Alex Patterson Date: Thu, 10 Oct 2024 13:57:28 -0400 Subject: [PATCH 07/13] added in 1.45 --- .../_account-management-troubleshooting.mdx | 8 -------- 1 file changed, 8 deletions(-) diff --git a/astro/src/content/docs/lifecycle/manage-users/account-management/_account-management-troubleshooting.mdx b/astro/src/content/docs/lifecycle/manage-users/account-management/_account-management-troubleshooting.mdx index 9e47ef8cc9..bc27c5a382 100644 --- a/astro/src/content/docs/lifecycle/manage-users/account-management/_account-management-troubleshooting.mdx +++ b/astro/src/content/docs/lifecycle/manage-users/account-management/_account-management-troubleshooting.mdx @@ -21,11 +21,3 @@ To set a self service form, click under Applications-> Edit Application Edit Application Screen - Registrations Select the form you would like to use. A default form is shipped with FusionAuth. - -## Trapped In The Login Screen - -If the user unchecks the Remember me checkbox, or if the checkbox is hidden and defaults to `false`, the user will not be able to view account management pages. Instead, the user will be continuously asked to log in, and no longer how many times they do so, they will never arrive at the self-service account management pages. - -This is because these pages use the SSO session managed by FusionAuth. If the user opts out of the SSO session by unchecking Remember me, the SSO session is disabled, and these pages are no longer available. - -There is a discussion in [GitHub Issue 1546](https://github.com/FusionAuth/fusionauth-issues/issues/1546) on modifying the implementation of the self-service account management pages to remove dependency on the SSO session, which would remove the requirement for users to check Remember me on the login screen. From 7c9e26d44f1e7fcb564e1471f7a32dcf83d63ef7 Mon Sep 17 00:00:00 2001 From: Alex Patterson Date: Thu, 10 Oct 2024 14:00:24 -0400 Subject: [PATCH 08/13] 1699 --- .../core-concepts/_logout-behavior-all-applications.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/astro/src/content/docs/get-started/core-concepts/_logout-behavior-all-applications.mdx b/astro/src/content/docs/get-started/core-concepts/_logout-behavior-all-applications.mdx index 7840ccfb09..cb705a3413 100644 --- a/astro/src/content/docs/get-started/core-concepts/_logout-behavior-all-applications.mdx +++ b/astro/src/content/docs/get-started/core-concepts/_logout-behavior-all-applications.mdx @@ -1,4 +1,4 @@ An Application's OAuth configuration allows you to specify the logout behavior of an application as either "All applications" or "Redirect only." Specifying the default value of "All applications" will call the configured logout URL for each application in the Tenant _except_ for the FusionAuth admin application. -As of version 1.37, this is no longer a limitation. See the [GitHub issue](https://github.com/FusionAuth/fusionauth-issues/issues/1699) for more information. +As of version [1.37](/docs/release-notes/#version-1-37-0), this is no longer a limitation. See [release notes](/docs/release-notes/#version-1-37-0) for more information. From 6669ccb3d5788b6369680f50449f38cf406adbc7 Mon Sep 17 00:00:00 2001 From: Alex Patterson Date: Thu, 10 Oct 2024 14:06:13 -0400 Subject: [PATCH 09/13] 1939 --- .../_identity-provider-login-method-request-parameter.mdx | 2 +- .../authenticate-users/identity-providers/social/google.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/astro/src/content/docs/apis/identity-providers/_identity-provider-login-method-request-parameter.mdx b/astro/src/content/docs/apis/identity-providers/_identity-provider-login-method-request-parameter.mdx index f57b53a096..4217afb094 100644 --- a/astro/src/content/docs/apis/identity-providers/_identity-provider-login-method-request-parameter.mdx +++ b/astro/src/content/docs/apis/identity-providers/_identity-provider-login-method-request-parameter.mdx @@ -11,6 +11,6 @@ import APIField from 'src/components/api/APIField.astro'; {props.idp_type === 'Google' && <> Since 1.44.0
- If you are using a version of FusionAuth older than 1.44.0, UsePopup won't work. UseRedirect will continue to work after this date. Please see Issue #1939 for more. This forum post has more details on an available workaround and upgrade process. + If you are using a version of FusionAuth older than 1.44.0, UsePopup won't work. UseRedirect will continue to work after this date. Please see [release 1.44.0](/docs/release-notes/#version-1-44-0) for more information. This forum post has more details on an available workaround and upgrade process. } diff --git a/astro/src/content/docs/lifecycle/authenticate-users/identity-providers/social/google.mdx b/astro/src/content/docs/lifecycle/authenticate-users/identity-providers/social/google.mdx index 7df60664c9..651aa580ba 100644 --- a/astro/src/content/docs/lifecycle/authenticate-users/identity-providers/social/google.mdx +++ b/astro/src/content/docs/lifecycle/authenticate-users/identity-providers/social/google.mdx @@ -121,7 +121,7 @@ This will take you to the `Add Google` panel, and you'll fill out the `Client Id Since 1.44.0 - **If you are using a version of FusionAuth older than 1.44.0**, `Use popup for login` won't work. `UseRedirect` will continue to work after this date. Please see [Issue #1939](https://github.com/FusionAuth/fusionauth-issues/issues/1939) for more. This [forum post](/community/forum/topic/2329/upcoming-google-identity-provider-changes) has more details on an available workaround and upgrade process. + **If you are using a version of FusionAuth older than 1.44.0**, `Use popup for login` won't work. `UseRedirect` will continue to work after this date. Please see [release 1.44.0](/docs/release-notes/#version-1-44-0) for more information. This forum post has more details on an available workaround and upgrade process. The text to be displayed in the button on the login form. This value is defaulted to `Login with Google` but it may be modified to your preference. From e730698d7d320aa11751737dd943d54003a39cee Mon Sep 17 00:00:00 2001 From: Alex Patterson Date: Thu, 10 Oct 2024 14:07:57 -0400 Subject: [PATCH 10/13] 2237 --- astro/src/content/docs/customize/look-and-feel/helpers.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/astro/src/content/docs/customize/look-and-feel/helpers.mdx b/astro/src/content/docs/customize/look-and-feel/helpers.mdx index d9c7b441ed..5f83644a1d 100644 --- a/astro/src/content/docs/customize/look-and-feel/helpers.mdx +++ b/astro/src/content/docs/customize/look-and-feel/helpers.mdx @@ -190,5 +190,5 @@ If you wish to enable an [invisible reCAPTCHA](https://developers.google.com/rec ``` From d95bdd6d45e82d0d4792886a54a2bcec78724f75 Mon Sep 17 00:00:00 2001 From: Alex Patterson Date: Thu, 10 Oct 2024 14:09:31 -0400 Subject: [PATCH 11/13] 2736 --- .../authenticate-users/logout-session-management.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/astro/src/content/docs/lifecycle/authenticate-users/logout-session-management.mdx b/astro/src/content/docs/lifecycle/authenticate-users/logout-session-management.mdx index 7656a38751..ea66f7b372 100644 --- a/astro/src/content/docs/lifecycle/authenticate-users/logout-session-management.mdx +++ b/astro/src/content/docs/lifecycle/authenticate-users/logout-session-management.mdx @@ -12,7 +12,7 @@ import InlineField from 'src/components/InlineField.astro'; import InlineUIElement from 'src/components/InlineUIElement.astro'; import Breadcrumb from 'src/components/Breadcrumb.astro'; import JSON from 'src/components/JSON.astro'; -import {RemoteCode} from '@fusionauth/astro-components'; +import { RemoteCode } from '@fusionauth/astro-components'; import ApplicationManagedSessionsStart from 'src/diagrams/docs/lifecycle/authenticate-users/application-managed-sessions-start.astro'; import ApplicationManagedSessionInvalid from 'src/diagrams/docs/lifecycle/authenticate-users/application-managed-session-invalid.astro'; import ApplicationManagedSessionsRequests from 'src/diagrams/docs/lifecycle/authenticate-users/application-managed-sessions-requests.astro'; @@ -426,7 +426,7 @@ The FusionAuth SSO session allows transparent authentication on one browser or d * the refresh token representing the FusionAuth SSO session is revoked via an API call or the admin UI From 186900ca9abd2e530ae6fcba46531fee24f4efb0 Mon Sep 17 00:00:00 2001 From: Alex Patterson Date: Thu, 10 Oct 2024 15:41:39 -0400 Subject: [PATCH 12/13] fix doc link --- .../content/docs/lifecycle/migrate-users/general-migration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/astro/src/content/docs/lifecycle/migrate-users/general-migration.mdx b/astro/src/content/docs/lifecycle/migrate-users/general-migration.mdx index b4e1752c3c..ac36b7ab22 100644 --- a/astro/src/content/docs/lifecycle/migrate-users/general-migration.mdx +++ b/astro/src/content/docs/lifecycle/migrate-users/general-migration.mdx @@ -501,7 +501,7 @@ FA_HOST=... curl -H "Authorization: $API_KEY" $FA_HOST'/api/user/search?queryString=data.migrated%3Atrue%0A' ``` -This will return all the users who've been migrated as well as a count, subject to the limits of FusionAuth's Elasticsearch integration. See [Maximum Users Returned Workarounds](https://fusionauth.io/docs/get-started/core-concepts/limitations#maximum-users-returned-workarounds) for how to get more from search. Here's an example of the output: +This will return all the users who've been migrated as well as a count, subject to the limits of FusionAuth's Elasticsearch integration. See [Maximum Users Returned Workarounds](/docs/get-started/core-concepts/limitations#maximum-users-returned-workarounds) for how to get more from search. Here's an example of the output: ```json title="Results of the FusionAuth migrated user query" {"total":629,"users": [ ... ] } From 7388f46b3e0f53240762d8c7c80230b70af454bf Mon Sep 17 00:00:00 2001 From: Alex Patterson Date: Thu, 10 Oct 2024 15:57:44 -0400 Subject: [PATCH 13/13] urls ugh --- .../lifecycle/authenticate-users/logout-session-management.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/astro/src/content/docs/lifecycle/authenticate-users/logout-session-management.mdx b/astro/src/content/docs/lifecycle/authenticate-users/logout-session-management.mdx index ea66f7b372..8eb89c0ff5 100644 --- a/astro/src/content/docs/lifecycle/authenticate-users/logout-session-management.mdx +++ b/astro/src/content/docs/lifecycle/authenticate-users/logout-session-management.mdx @@ -426,7 +426,7 @@ The FusionAuth SSO session allows transparent authentication on one browser or d * the refresh token representing the FusionAuth SSO session is revoked via an API call or the admin UI