standards Issue/718 check for key manager

changed the request method to check user role slightly to session-token based approach and added retry-option, if 401 occures for requesting specialized scope, also added a small method to match different kinds of auth-urls with the valid path to request user roles from barbican

Sep 25 '24 11:09 fraugabel

i will change that thanks

Oct 01 '24 13:10 fraugabel

One remark regading print: once we have devised the formal test cases, we can and should use print for those; see item 3 in this section of scs-0003-v1

Oct 07 '24 13:10 mbuechse

As expected, I was able to remove a whole lot of code by using the openstacksdk properly.

the problem is that it gives me the ERROR: ForbiddenException: 403: Client Error for url: https://(...)/secrets, Forbidden on for instance our yaook os, where i could get a decent response before, that's why we used the former approach

Oct 23 '24 12:10 fraugabel

the problem is that it gives me the ERROR: ForbiddenException: 403: Client Error for url: https://(...)/secrets, Forbidden on for instance our yaook os, where i could get a decent response before, that's why we used the former approach

I would need the whole output to understand that.

I can imagine that this could be fixed by changing the clouds.yaml. Let's have a look on Monday.

Oct 23 '24 14:10 mbuechse

I checked again, and it works better than what's in the main branch. However, the output is not usable. See my comment for the other check.

Oct 25 '24 07:10 mbuechse

@fraugabel I reworked a few parts. I think it's usable now. However, before approving, I ask you to check yourself once more.

Oct 29 '24 09:10 mbuechse