Clarify audience and clients #701

[panta-123]

• Clairfy audience registration in IdP.
• Turns out only one client is needed and use for both auth and transfers.
• clarify comma in id and make it single line
• make json example valid json

[Soap2G]

Hi @panta-123, many thanks for these clarifications!

Aside from a couple of cosmetic suggestions, just one main question: am I understanding correctly that we only need 1 client to manage both users authN + authZ for 3rd party transfers / daemons? And therefore the C1/C2 business we had before is not really used anymore?

In this case I think it's worth mentioning that the same client will manage both; I liked the explanation for the usage of the two clients before, and I think it's worth keeping an updated description for clarity.
This includes for instance elaborating on what each grant type addresses.

I didn't have the opportunity yet of testing the transfers setup, but by reading it looks good.
Will try to test stuff in the next days.

[panta-123]

Hi @panta-123, many thanks for these clarifications!

Aside from a couple of cosmetic suggestions, just one main question: am I understanding correctly that we only need 1 client to manage both users authN + authZ for 3rd party transfers / daemons? And therefore the C1/C2 business we had before is not really used anymore?

I tested it in dev server and thats the conclusion I made. Would love to have second person opinion after testing or already using it. May be @maxnoe , are you already using it ?

In this case I think it's worth mentioning that the same client will manage both; I liked the explanation for the usage of the two clients before, and I think it's worth keeping an updated description for clarity. This includes for instance elaborating on what each grant type addresses.

Okay will add that in next commit.

I didn't have the opportunity yet of testing the transfers setup, but by reading it looks good. Will try to test stuff in the next days.