Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

credentialList should be whitelist in step 6, 1st bullet, of getAssertion() processing rules #111

Closed
equalsJeffH opened this issue Jun 1, 2016 · 0 comments

Comments

@equalsJeffH
Copy link
Contributor

step 6 of getAssertion() processing rules says in part...

6. For each embedded or external authenticator currently available on this platform, perform 
the following steps:

  * If whitelist is undefined or empty, let credentialList be a list containing a single wildcard 
     entry.

  * If whitelist is defined and non-empty, optionally execute a platform-specific procedure to 
    determine which of these credentials can possibly be present on this authenticator. Set 
    credentialList to this filtered list. If credentialList is empty, ignore this authenticator and 
    do not perform any of the following per-authenticator steps.

It seems that the first bullet item ought to read...

  * If whitelist is undefined or empty, let whitelist be a list containing a single wildcard 
     entry.

..otherwise the processing in the 2nd rule does not make sense because whitelist may be undefined or empty, while a credentialList containing a wildcard has been created, which does not make sense in the 2nd bullet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants