Changed: updated release notes

doc/release-notes/10959-oidc-api-auth-ext.md

@@ -3,7 +3,12 @@ where ``BearerTokenAuthMechanism`` successfully validates the token but cannot i
 is no account associated with the token.
 
 To register a new user who has authenticated via an OIDC provider, a new endpoint has been
-implemented (``/users/register``). A feature flag called ``api-bearer-auth-provide-missing-claims`` has been implemented to allow
+implemented (``/users/register``). A feature flag named ``api-bearer-auth-provide-missing-claims`` has been implemented
+to allow
 sending missing user claims in the request JSON. This is useful when the identity provider does not supply the necessary
 claims. However, this flag will only be considered if the ``api-bearer-auth`` feature flag is enabled. If the latter is
 not enabled, the ``api-bearer-auth-provide-missing-claims`` flag will be ignored.
+
+A feature flag named ``api-bearer-auth-handle-tos-acceptance-in-idp`` has been implemented. When enabled, it specifies
+that Terms of Service acceptance is managed by the identity provider, eliminating the need to explicitly include the
+acceptance in the user registration request JSON.