Thomas Krille
Thomas Krille
In #244, we only removed the REST endpoints for PATCHing resources. All the other stuff must be removed too. @dacrome already did most of the work for this, so this...
Every user in OSIAM has an origin, that is either `internal` (OSIAM owns the user data) or `ldap` (an LDAP server owns the user data). Currently, the storage of this...
@bng-okta [suggested](https://github.com/osiam/osiam/issues/131#issuecomment-182929365), that supporting the [well-defined enterprise extension](https://tools.ietf.org/html/rfc7643#section-4.3) is a viable alternative to supporting arbitrary complex fields in extension. First Question is: Do we want to add this feature and...
We should add documentation about how OSIAM is versioned. This should contain some of the following things: - Versioning strategy - [Semantic Versioning](http://semver.org/) - Do we omit the PATCH version...
It would be nice, if the bundle was automatically tested against a real Dropwizard app. Even nicer, if it's tested against each officially supported version.
This might be interesting for users of Heroku or other PaaS that define the database connection parameters as a single URL.
Most assertions in the tests are totally crappy. Improve this!