Okay, that was it! So I accidentally switched both policies and applied the wrong bind/dial.
Thanks a lot!
There are a couple of recommendations in regards to UX I can give when working with the console, please let me know what you think of it. If you agree I’ll open a Github issue:
When creating service policies, there’s no way to know if a role attribute exists. Maybe like with identities, offer a dropdown to select an existing one? The same applies for creating identities, offer a list of already existing role attributes, otherwise I’ll always have to find an existing identity with the same attribute, remember the exact name etc.
Auto remove whitespaces before names of identities, services etc. I’ve copied a service name from a textfile and also copied a space before which caused some headache
For service configurations, allow to not set a timeout (and set a default value?) as one is also able to omit the timeout when using the CLI
Other than that I am definitely up and working Everything’s working for my infrastructure now as expected, thanks for the help again!
@TheLumberjack any update on release for BrowZer in CloudZiti and/or OSS? Did I miss it? Agentless workflows are about at the top of my list of concerns for my particular use-case.
It’s not quite ready for public consumption but making it ship shape for eager testers like yourself is something @curt is busy working on. Speaking of which, he has solicited “eager” individuals who would want to try it out early. Maybe you’re interested?
@curt what else can you add, I’m sure I missed something!
@floucks here is a link to a post I made over the weekend. In it, there is a link to an opt-in form where folks can express interest in early availability pilots.
