On 15 August 2014 19:25, <[email protected]> wrote: > Does Isis in its present state lend itself for large quantities of users > who can register hemselves and maintain their own personal records/details > (like in a simple CMS)
The authentication layer (that sits underneath Shiro) is pluggable, so the user records can be held in any format. However, there isn't anything in Isis to allow self-registration. > or is it better to handle that on a future front-end angular app apart > from Shiro? What would you advice? At the moment I find it hard to > oversee... > > Yes, you'd need to write something to do the registration. This could be custom pages written in Wicket, for example, or a RESTful app as you suggest. Cheers Dan > But anyway: I need the objects in ISIS and will continue to build them ;-) > > > @javax.inject.Inject > private DomainObjectContainer container; > > and then: > > String userName = container.getUser().getName(); > > > > > On 15 August 2014 18:34, wrote: > > > In my Socrates app I created a class 'login' to manage future user > > front_end logins. How can I set the relationship between user and login > so > > that each user can have at most one login? > > > > > > > > > > > > > > > >
