[Openid-specs-fapi] [Bitbucket] Issue #123: Is it okay for request object URNs to be predictable? (openid/fapi)

[Edmund Jay]

[edmund_jay]
Edmund Jay commented on issue #123:
Is it okay for request object URNs to be predictable?<https://bitbucket.org/openid/fapi/issues/123/is-it-okay-for-request-object-urns-to-be>

Part 2: Tidy up wording around request object

request object URLs /and/ URNs should be cryptographicly random.

It also seems unsuitable to have a 'shall' clause within the introduction, so the requirement is moved to the 'response' section.

I also took this opportunity to number the clauses as per other sections, so they're easier to refer to in external documents etc.

closes #123<https://bitbucket.org/openid/fapi/issues/123/is-it-okay-for-request-object-urns-to-be>

→ <<cset 3dc41078ab7c<https://bitbucket.org/openid/fapi/commits/3dc41078ab7c>>>


Status: new closed



View this issue<https://bitbucket.org/openid/fapi/issues/123/is-it-okay-for-request-object-urns-to-be> or add a comment by replying to this email.

Unsubscribe from issue emails<https://bitbucket.org/api/1.0/repositories/openid/fapi/issue/123/unsubscribe/openid/df2bfe7836723d6e685249a416e7c899130d4b87/> for this repository.               [Bitbucket]  <https://bitbucket.org>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-fapi/attachments/20171003/f16b1129/attachment-0001.html>