Add simple identity store to get started

[arjantijms]

The currently provided identity stores for LDAP and JDBC require some effort to populate.

Especially for people new to the platform, and even more so for example code, something simpler is required.

The biggest challenge is not in defining something simpler, but in getting it through the process. In the past there's always that one person who thinks it's insecure to have a simple store, and subsequently the proposal is withdrawn again.

[m-reza-rahman]

I've always tried to support this. I suggest committers vote on a formal proposal using the normal consensus process.

[hantsy]

I remember the original version had an In Memory implementation, but not included in the final version.

[arjantijms]

I remember the original version had an In Memory implementation, but not included in the final version.

Indeed. It's still in Soteria, but someone raised a concern that it may not be secure, so it was left out of the spec.

See; https://github.com/eclipse-ee4j/soteria/blob/master/impl/src/main/java/org/glassfish/soteria/identitystores/EmbeddedIdentityStore.java

[hantsy]

It is good for demonstration and writing tests purpose.

Spring Security also provides in-memory Map based UserDetialsService,eg https://github.com/spring-projects/spring-security/blob/main/core/src/main/java/org/springframework/security/core/userdetails/MapReactiveUserDetailsService.java.

But Embedded here confuse a little for me with JPA @Embeddalbe and @EmbeddedId.

[arjantijms]

But Embedded here confuse a little for me with JPA @Embeddalbe and @EmbeddedId.

InMemmory would be fine too. I can rename it to that for the M1 release.

M1 is meant for feedback and to show progress. Nothing in it necessarily has to be like that in the final version, so we can allow ourselves some freedom.

[arjantijms]

@hantsy @m-reza-rahman see #304