Hi Yong, I am not sure what the entire list of secrets stored in barbican is, but I know if you specify credentials for external docker registry to bootstrap the system with, barbican secrets will be created for those. Thanks, Jerry -----Original Message----- From: Yong Hu <yong.hu@intel.com> Sent: Tuesday, December 3, 2019 10:34 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] How is Barbican being used in StarlingX? Hi folks, I am working on a LP and might like to use "barbican-keystone-listener" to monitor a keystone event. From "sm-dump", we are seeing "barbican-api", "barbican-keystone-listener" and "barbican-worker" are "enabled-active", but I have a few questions about how Barbican (on host) is being used in StarlingX: 1. what secrets are stored in Barbican currently? btw: I got nothing by running "openstack secret list" or "barbican secret list". As well, "admin" and its password are stored in Keyring, not in Barbican. 2. Does "barbican-keystone-listener" actually work with keystone in StarlingX? I enabled "debug" flag in /etc/barbican/barbican.conf, but when I was triggering events with keystone, it seemed there was no notifications captured by "barbican-keystone-listener". 3. there is a "barbican" user/identify (with initial password) managed by keystone, but I wonder what we used this "barbican" for StarlingX. thanks in advance! -Yong _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss