Laurent Broudoux

Hi @fhopfensperger Could you explain the motivation with this PR? We had previous discussion (like for example in #320) about that and ended-up with it not being a harde requirement...

Hey @trinhpham, Updating to the latest Keycloak-X is something we should handle in near future. It's great to share your experiment with it. I think you probably had to also...

Hi @sdupont Thanks for opening this issue. Corporate Proxy is not a supported feature for the moment. The old variables `network.username` and `network.password` are not used in a consistent way...

Hi @sdupont I pushed some enhancements to manage HTTP(S) corporate proxy. I've tested with the Squid proxy using basic authentication. Changes should be available into the `quay.io/microcks/microcks:latest` container image in...

Hi @sdupont Any update on this one? Did you find time testing this out? Thanks for feedback,

Yeah I see what you mean ... These are ugly in documentation ... Problem is that there is no "good" or "bad" examples, all of them are treated equally by...

Thanks for opening this issue. You're right : currently there's no user feedback to inform of incorrect message templating issues. That would be a nice enhancements. Need to think about...

Maybe @nmasse-itix you could help on this one ? This may just be a Keycloak configuration documentation issue ?

If it could be of any help, I've found this [blog post](https://stories.scandiweb.com/sign-in-to-amazon-aws-using-saml-protocol-and-keycloak-as-identity-provider-e3798387de99) that describe this configuration. There's also this [part of Keycloak's doc](https://www.keycloak.org/docs/latest/server_admin/index.html#default_identity_provider) that mention how to configure a default...

Hi @jonathanvila, thanks for raising this complex issue ;-) At the origin - I would say "by design" - Microcks is not intended to solve this testing use-case that is...