Ruud Senden

We don't need to cover every possible SSC API in v1.0, and I see this as lesser priority than some other tasks, so I'd like to suggest moving this to...

Reason why I stated there are more important tasks to focus on is that I think we should focus first on functionality for end users, like enabling pipeline integrations. Administrative...

There are already commands for managing users under `fcli ssc access-control`, including a `create-local-user` command. Managing LDAP entities is discussed in #46, so this issue can be closed.

Non-20x responses now generate an exception. We have chosen to just propagate the exception to the user, rather than trying to wrap it in the configured output format. This ensures...

When encountering an error, we mostly throw standard Java exceptions like IllegalStateException/IllegalArgumentException, with hardcoded messages. Better would be to use custom exceptions that include a message resource key, to allow...

We only support English language for now, so the ability to support internationalized error messages is low priority for now. Eventually we should come up with some generic best practices...

Closing as fcli v3.0.0 introduces several improvements and a more structured approach for example handling with its own `AbstractFcliException` class hierarchy

We can potentially use progress writers for this.

All commands related to access control are now in `fcli ssc access-control`, so we can easily add commands for managing LDAP groups under that entity.

Maybe related to #369, in case we'd like to provide functionality for assigning/removing multiple users from a single role.