Monday, 2021-04-19

*** tkajinam has quit IRC01:06
*** tkajinam has joined #openstack-barbican01:07
*** redrobot0 has joined #openstack-barbican04:07
*** redrobot has quit IRC04:11
*** redrobot0 is now known as redrobot04:11
*** Luzi has joined #openstack-barbican06:37
*** xek has joined #openstack-barbican07:09
*** tosky has joined #openstack-barbican08:03
*** xek has quit IRC09:11
*** xek has joined #openstack-barbican09:15
tridentDoes an issue with creating secrets without a name specified resulting in breaking that users context completely even for "openstack secret list" (error: "4xx Client error: Forbidden: Secret retrieval attempt not allowed - please review your user/project privileges" ring a bell? Creating the exact same secret _with_ a specified name works. Train / p11_crypto_plugin / thales DPoD.09:23
tridentThe most puzzling thing is that in another region with the same versions and configuration it seems to work just fine.09:24
tridentAny hints on where to start looking?09:25
*** iurygregory has joined #openstack-barbican10:17
*** ricolin has quit IRC12:15
*** d34dh0r53 has joined #openstack-barbican12:46
redrobothi trident12:46
redrobottrident seems like a RBAC permissions error.  It should not be related to the name property, I think.12:47
tridentredrobot: openstack secret store --secret-type symmetric causes the issue while openstack secret store --secret-type symmetric --name foo works, so it doesn't seem like it.13:06
redrobottrident same credentials?13:07
tridentredrobot: Yes.13:07
redrobottrident for both store/retrieve?13:07
*** rajivmucheli has joined #openstack-barbican13:07
tridentredrobot: It _does_ in fact store it. But can't retreive it if it doesn't have a name.13:08
redrobotHmm... that's weird13:09
redrobottrident what roles are assigned to the user?13:09
rajivmucheliHi, i see there are online blogs/articles to integrate Barbican/HSM but its a mix & match. Is there an entire workflow doc available ?13:09
tridentredrobot: That's why "openstack secret list" breaks as well as the clients attempt to GET the secret after storing it.13:09
rajivmuchelialso is there a doc to migrate from Simple Crypto Plugin to HSM ?13:10
tridentredrobot: Implied roles. Both creator and reader. And exactly the same in the region where it works.13:10
redrobottrident ah, I see.  yeah, neither "creator" nor "reader" is allowed to retrieve a secret in the default policy13:11
tridentredrobot: Really? Docs seem to say: "They are also allowed full access to existing secrets owned by the project in scope." for creator role...13:14
redrobottrident actually, I'm confused now ...  the old policy should allow "creator" to retrieve a secret.13:14
redrobottrident looking at https://docs.openstack.org/barbican/latest/admin/access_control.html13:14
redrobotWe did implement the new unified "secure-rbac" policy for wallaby13:15
redrobotbut the old policy is still the default13:15
tridentredrobot: And that would still not explain why it would work perfectly with a name, but not without one...13:15
redrobotYeah, that is strange.13:15
redrobottrident mind opening a bug story: https://storyboard.openstack.org/#!/project/openstack/barbican ?13:16
tridentredrobot: Yeah, I'll collect some information and get something in there! Thanks for the response!13:17
redrobotrajivmucheli hi, have you looked at https://docs.openstack.org/barbican/latest/install/barbican-backend.html13:19
redrobotspecifically https://docs.openstack.org/barbican/latest/install/barbican-backend.html#pkcs-11-crypto-plugin13:20
redrobotthe workflow is:13:21
redrobot1. edit the conf file to set the correct parameters for your HSM13:21
redrobot2. Create the MKEK and HMAC keys in the HSM using the barbican-manage CLI tool13:21
redrobot3. restart barbican13:21
*** rajivmucheli55 has joined #openstack-barbican13:21
redrobotWe don't have a "migration" per-se, but you can use multiple backends to configure both simple crypto and pkcs#11 at the same time13:22
redrobotyou can default to pkcs#11 for new secrets while still making the old secrets available with simple-crypto13:22
rajivmucheli55thanks, yes i did, which is the best vendor to pick ? if cost is not a constraint for a multi-tenant & multi-region setup ?13:23
rajivmucheli55is the soft-hsm module production ready ?13:24
*** rajivmucheli has quit IRC13:25
redrobotI'm not sure what you mean by "soft-hsm" ?  If you're referring to the SoftHSM library provided by the DNSSec group, then it may work, but we don't test it currently13:25
rajivmucheli55https://github.com/openstack/charm-barbican-softhsm13:26
redrobotHmm... interesting.  Yeah, that's SoftHSM.  Our team doesn't maintain that charm though, and as they noted it may currently be broken.13:27
rajivmucheli55oh ok, then i would invest time on this. So coming back to the question, which is the best vendor to pick ? if cost is not a constraint for a multi-tenant & multi-region setup ?13:28
redrobot> cost is not a constraint < nice!13:30
rajivmucheli55:)13:30
redrobotThales Luna Network HSM is worth considering as they provide good support for HA configurations.13:31
redrobotAlso take a look at Entrust nCipher13:31
redrobotI don't have any experience with Utimaco, so I can't comment on those13:31
redrobotATOS are fine, but the HA support is not ideal13:32
rajivmucheli55oh ok, thanks13:32
rajivmucheli55is there a doc on hardware side ? like how to setup communication, networking, etc13:33
redrobotWhen you decide on a vendor for your HSM they should make all that available to you13:33
rajivmucheli55oh ok.13:33
redrobotYou can get an idea of how things work by looking that the ansible-role-XXXX-hsm roles we provide13:33
redrobothttps://opendev.org/openstack/ansible-role-lunasa-hsm for example13:34
rajivmucheli55nice13:35
*** rajivmucheli55 has quit IRC13:40
*** raildo has joined #openstack-barbican13:42
*** ricolin has joined #openstack-barbican13:50
*** dave-mccowan has quit IRC14:57
*** d34dh0r53 has quit IRC15:11
*** d34dh0r53 has joined #openstack-barbican15:25
*** Luzi has quit IRC16:31
*** raildo_ has joined #openstack-barbican16:56
*** raildo has quit IRC16:59
*** raildo_ has quit IRC20:36
*** lxkong has quit IRC20:38
*** gagehugo has quit IRC20:38
*** mnasiadka has quit IRC20:38
*** gagehugo has joined #openstack-barbican20:38
*** lxkong has joined #openstack-barbican20:38
*** mnaser has quit IRC20:38
*** mnasiadka has joined #openstack-barbican20:39
*** mnaser has joined #openstack-barbican20:39
*** tosky has quit IRC23:23

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!