Hello,
Yes, I interpreted it as it can provide null value if it wants to. And,
since it is listed as one of the parameters to add, I assumed it would,
otherwise, put the profile value.
In any case, it is not a huge problem from my side to remove it from the
mqtt draft.
Kind regards,
--Cigdem
On
Hi Ludwig,
Thank you for the lightning quick reply! I think that maybe something on the
lines of “The client MUST NOT send a non-empty “ace_profile” parameter.” in
5.6.1. I think the confusion might have come from the term “can”, “it can send
an empty parameter” does not imply that “it must
Hello Francesca, Cigdem,
I believe I know the reason for the confusion: Earlier versions of the
framework allowed the clients to indicate a preference for a specific profile
by sending in values with the “ace_profile” parameter in the access token
request.
This option was removed because we
Hi Cigdem,
Thanks for the quick reply! Answers inline.
To Ludwig and the WG, which might not otherwise see the comment: Cigdem and I
have a different interpretations of what the framework allows to put in the
“ace_profile” parameter in the request from Client to AS (See (***) below). I
think
