I would also like to have this functionality available; the solution with a hook in #4 worked fine as well though, thanks!
I am also running into this issue.
Note that it also happens when giving a role the general 'administer users' permission as this removes that role from the administerusersbyrole configuration and hence the associated dynamic permissions also disappear.
Adding dependencies as mentioned looks like a good solution.
woutgg → created an issue.
woutgg → created an issue.
I see, that makes sense.
In my case, I had no access the Azure portal itself and a bit of potentially important information was also truncated: namely the suggestion that secret key and secret ID might have been swapped (I do not have the exact message at hand). Additionally, seeing the client secret in the full message helped me to be more confident I did not misconfigure the module itself.
I agree that in the choice between this shortcoming and revealing the client secret, the latter if probably more important in most cases.
Perhaps an override toggle might be useful though, to enable in a dev environment for instance?
Yes, the text I quoted is the literal message in the log entry.
The full message does still exist though, as I could access it via the temporary statement I mentioned.
woutgg → created an issue.
woutgg → created an issue.
This warning was emitted on every run of `drush cr` (Drupal 10.1.1). Just applied the patch from #5 and it works fine.
I've only just found out about this issue via Drupal's status report while upgrading from 9.3.9 to 10.1.1 so I have applied the the patch from #64. Everything appears to be in order: updates were run, the column has been added and the module functions fine.
Thanks for your work!