[Server] [Client] Return BadIdentityTokenInvalid if use of anonymous identity token is not allowed #3012
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Return StatusCode.BadIdentityTokenInvalid instead of BadUserAccessDenied if the Client sends an AnonymousIdentityToken or no identity Token at all. This makes the Server pass UA CTT SessionService -> SessionBase -> TestCases -> Err-009
Make the Client throw a ServiceResultException BadIdentityTokenInvalid instead of BadUserAccessDenied to be consistent with the response a server would send. This is relevant as our client does a "pre-check" if the endpoint supports the provided policy before sending the request to the server
Related Issues
Types of changes
Checklist