Update doc to include IS-10

[lo-simon]

Update documents and diagrams to include IS-10 implementation.

[garethsb]

@lo-simon Are the settings.h changes meant to be in this PR? They look related to IS-12, not IS-10.

Edit: Apart from the actual change mentioned in the commit comment "highest_pri and lowest_pri are used in Node only", of course!!

[lo-simon]

Thanks, @garethsb, you are right, I must be using the IS-12 branch while doing the document update, I will fix it now.

[lo-simon]

Edit: Apart from the actual change mentioned in the commit comment "highest_pri and lowest_pri are used in Node only", of course!!

When Authorization was implemented, highest_pri and lowest_pri were also used for the Authorization API, but then during the implementation phase, I noticed the Authorization API will well be not be running on the Registry, i.e. should not be using the same pri range as the Registration/Query API.

[garethsb]

What's changed here? 🤔

[jonathan-r-thorpe]

This diagram still shows the Device Code Flow grant type in it which should perhaps be removed?

[lo-simon]

Well spotted, I will remove Device Code Flow grant

[jonathan-r-thorpe]

A bit confused by the Authorization Process box at the bottom of the diagram. This contains a Client Credentials Flow box which suggests this is process is infinitely recursive!!!

[lo-simon]

I am trying to show once the connection is broken between Auth server & the Node, Node will start over again to fetch Auth server metadata.... and Client Credentials flow

[jonathan-r-thorpe]

Similar to the Client Credentials diagram, the Authorization Process box at the bottom of the diagram contains an Authorization Code Flow box suggesting an infinite recursion :|

[jonathan-r-thorpe]

Not sure what the "Is required to access protected API?" diamond is asking. Also on "No" it enters the "do authorization_operation" loop which only seems to exit on Failed - is that right?

[jonathan-r-thorpe]

If it's a separate process (like the "start authorization code flow" box) should it perhaps be "start authorization_operation loop"? (same applies I guess to the authorization_operation box at the bottom of the diagram)

[jonathan-r-thorpe]

LGTM