I have the same question.

Users are added in a non-traditional way in which you create a project first, then invite them. The process is automated from there and gives you the opportunity to use a collaboration area for new members. Please give this some thought.

What if you want to allow users to register themselves? In the case of having the server inside a corporate network, only people who have access to the network could register themselves?

Or perhaps even a feature addition would be to allow users to register themselves but have the admin approve the registration. Most open-source forum softwares have this functionality.

The team elements server uses the following build.properties setting to enable registration:

1. Capabilities

REGISTER=true

Matt Rajkowski wrote:
The team elements server uses the following build.properties setting to enable registration:

1. Capabilities

REGISTER=true

I had to stop and restart the Apache service before the new settings would take effect. This doesn't seem like the best option for when updates are done, but because it is just a test environment I did it.

1) What is the normal process for including updates to the build.properties?

Upon restarting the service, the "Setup an Account" area showed up on the main page when not logged in. However, whenever someone who is not logged in clicks on it they will receive the following message: "*Please login, you session has expired"

2) Is there something else that needs to be done to enable users to register? Otherwise - what is the point of having the Setup an Account button on the front?

3) Also, what is the Recompile JSPs button used for?

PS. Thanks for the quick reply!

The Administration web page will be the normal process for making changes to build.properties -- this requires web-based editors so that admins can make changes on-the-fly. The framework is there, but not complete. In the meantime, editing the file manually works.

The next release will have an Install and Admin parameter for changing the registration property. This will be documented and tested too because it looks users are having trouble.

The intent is for the admin to choose from the following registration types:

1) Allow anyone to register (Undocumented and needs UI)
2) Only allow administrators to invite others (works today)
3) Allow any user to invite any other user (works today)
4) Allow users to register from an integrated system (tbd)

For your next question, when installing a JSP based web application, the JSPs (HTML files with code) are in an uncompiled state. This means that the application needs to compile the pages whenever they are needed, but does this only once.

You can choose to do this at Install, during an Upgrade, or if need be on the Admin page. This speeds of the application.

The recompile JSPs button is there for source code users to compile the JSPs. Typically installations have this on the Install and Upgrade pages, but if needed it's there in Admin.

Matt Rajkowski wrote:

The intent is for the admin to choose from the following registration types:

1) Allow anyone to register (Undocumented and needs UI)
2) Only allow administrators to invite others (works today)
3) Allow any user to invite any other user (works today)
4) Allow users to register from an integrated system (tbd)

What's the status of the registration functionality? It seems like (1) is almost there, but there are some bugs with enabling the REGISTER=TRUE functionality. And by option (4) do you mean LDAP, Active Directory, etc or something completely different?

Having LDAP or Active Directory integration would solve many of the registration issues for users with those systems.