AWS prescriptive-guidance documentation change
Summary
Updated author attribution format and removed bold formatting from table headers
Security assessment
Formatting changes to table headers and author credits. No security content modifications - authentication flow recommendations remain unchanged.
Diff
diff --git a/prescriptive-guidance/latest/patterns/choose-an-amazon-cognito-authentication-flow-for-enterprise-applications.md b/prescriptive-guidance/latest/patterns/choose-an-amazon-cognito-authentication-flow-for-enterprise-applications.md index 6e1bb3fba..430f8383f 100644 --- a//prescriptive-guidance/latest/patterns/choose-an-amazon-cognito-authentication-flow-for-enterprise-applications.md +++ b//prescriptive-guidance/latest/patterns/choose-an-amazon-cognito-authentication-flow-for-enterprise-applications.md @@ -9 +9 @@ SummaryPrerequisites and limitationsArchitectureToolsEpicsRelated resourcesAddit - _Created by Michael Daehnert (AWS) and Fabian Jahnke (AWS)_ + _Michael Daehnert and Fabian Jahnke, Amazon Web Services_ @@ -47 +47 @@ Use the following table to help you choose an authentication flow. More informat -**Do you need machine-to-machine authentication?**| **Is your app a web-based application where the frontend is rendered on the server?**| **Is your app a single-page application (SPA) or mobile-based frontend application?**| **Does your application require refresh tokens for a "keep me signed in" feature?**| **Does the frontend offer a browser-based redirect mechanism?**| **Recommended Amazon Cognito flow** +Do you need machine-to-machine authentication?| Is your app a web-based application where the frontend is rendered on the server?| Is your app a single-page application (SPA) or mobile-based frontend application?| Does your application require refresh tokens for a "keep me signed in" feature?| Does the frontend offer a browser-based redirect mechanism?| Recommended Amazon Cognito flow