Skip to main content

FAPI-RW-ID2-ENSURE-OTHER-SCOPE-ORDER-SUCCEEDS

NameEnsure a different scope ordering is still acceptable
CategoryINFOSEC
Execution MethodAUTOMATED (FAPI BASELINE)
Preconditions
Description

This test makes a FAPI authorization request but with the order of the entries in the 'scope' reversed, which must succeed. As per RFC6749 section 3.3, 'If the value contains multiple space-delimited strings, their order does not matter'. The reason for this test is that some OAuth clients process scopes in a way that the order they are sent to the server is not under the control of a developer using that client, and as per the spec such requests must still be accepted.

Steps
  1. Execute authorisation as per FAPI-RW-ID2-PAR however during calls for scope population (as per request object generation in (8) and request initiation) reorder the scope list to be different from the prescribed default
  2. It is expected the Holder will proceed as expected and is able to process scopes in any order
Inputs
Expected Results

The Holder must treat the scope list as a set and not as an ordered array