regen from jira using ./modules/release-notes/single-source-release-notes.py script

Signed-off-by: Nick Boldt <[email protected]>

Author: nickboldt

modules/release-notes/ref-release-notes-known-issues.adoc

@@ -27,11 +27,11 @@ Repositories might be added to Developer Hub from various sources (like statical
 * link:https://issues.redhat.com/browse/RHIDP-5284[RHIDP-5284]
 
 [id="known-issue-rhidp-4695"]
-== [Doc] OIDC refresh token behaviour 
+== [Doc] OIDC refresh token behavior 
 
-When using {rhsso-brand-name} or {rhbk-brand-name} as an OIDC provider, it should be noted that the default access token lifespan is set to 5 minutes.  This corresponds to the token refresh grace period set in {product-short} which is the threshold used to trigger a new refresh token call.  Since the token is always near expiration, this will cause performance issues from frequent refresh token requests.  It's recommended to increase the lifespan in the {rhsso-brand-name} or {rhbk-brand-name} serve by setting *Configure > Realm Settings> Access Token Lifespan* to a value that is greater than 5 minutes.  
+When using {rhsso-brand-name} or {rhbk-brand-name} as an OIDC provider, the default access token lifespan is set to 5 minutes, which corresponds to the token refresh grace period set in {product-short}. This 5-minute grace period is the threshold used to trigger a new refresh token call. Since the token is always near expiration, frequent refresh token requests will cause performance issues.
 
-
+This issue will be resolved in the 1.5 release. To prevent the performance issues, increase the lifespan in the {rhsso-brand-name} or {rhbk-brand-name} server by setting *Configure > Realm Settings > Access Token Lifespan* to a value greater than five minutes (preferably 10 or 15 minutes).
 
 .Additional resources