Clarify JWT Authentication (#958)

cerner · Jun 26, 2023 · c4aed4f · c4aed4f
1 parent 881cfba
commit c4aed4f
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/content/authorization.md b/content/authorization.md
@@ -1048,7 +1048,7 @@ curl -X POST 'https://authorization.cerner.com/tenants/ec2458f2-1e24-41c8-b71b-0
 
 #### JWT Authentication ####
 
-Alternatively, clients may authenticate themselves using signed JSON Web Tokens (JWTs). This process is similar to the above, but uses ``Authorization: Bearer`` instead. This is the preferred mode of authentication for [Bulk Data](http://hl7.org/fhir/uv/bulkdata/) clients. For complete details, see [Java Web Token (JWT)](https://www.rfc-editor.org/rfc/rfc7519) and [JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants](https://www.rfc-editor.org/rfc/rfc7523).
+Alternatively, clients may authenticate themselves using signed JSON Web Tokens (JWTs). This is the preferred mode of authentication for [Bulk Data](http://hl7.org/fhir/uv/bulkdata/) clients. For complete details, see [SMART App Launch: Backend Services](http://hl7.org/fhir/smart-app-launch/STU2/backend-services.html).
 
 Note that clients leveraging this type of authentication must also pre-register their JSON Web Key Sets (JWKS) using [Cerner Central System Account Management](https://wiki.cerner.com/display/CernerCentral/System+Account+Management+Help). For complete details, see [Managing JSON Web Key Sets in System Account Management](https://wiki.cerner.com/display/public/CernerCentral/Managing+JSON+Web+Key+Sets+in+System+Account+Management).