Messages - Do we need three ways of requesting "acr" values?

Issue #766 wontfix
Michael Jones created an issue

We currently have 3 ways of requesting "acr" values:

  1. The "default_acr_values" registration parameter.

  2. The "acr_values" request parameter.

  3. The "acr": {"values": ...} claim request.

Which of these should we keep?

Comments (6)

  1. Brian Campbell

    Seems like too many ways. Some kind of support for the "step up" use case is needed but one way is probably enough.

  2. Michael Jones reporter

    We could eliminate 2 if every trust framework using ACRs mandated support for requesting the "acr" claim in the "claims" request parameter.

  3. Michael Jones reporter
    • changed status to open

    There are reasons for all the methods in the spec. There isn't consensus to remove any of them.

    John said that there are privacy reasons to want to be able to request "acr" as an essential claim and return an error if it fails.

  4. Log in to comment