need to create this activation key based approach for user registration

[Migrated From Jforum.net]

Hi,

I needed to create this activation key based approach for user registration, that a user gets registered only when he:
1. fills the user creation form in application.
2. gets an email with an activation link
3. goes to the link to activate account

I noticed an entry in user POJO called activationKey. There's also a a method activateAccount in UserAction.

Any relations between the two? Any suggestions on how can i implement the new functionality resuing some stuff in here
[originally posted on jforum.net by vikram.arora.in]

[Migrated From Jforum.net]

This is already implemented. Just enable it at Admin Panel -> Configurations -> Mail -> Requires user to authenticate email

Rafael
[originally posted on jforum.net by Rafael Steil]

[Migrated From Jforum.net]

thanks Rafael !! u r the best!
[originally posted on jforum.net by vikram.arora.in]

[Migrated From Jforum.net]

I have Requires user to authenticate email enabled.
But the user can befor he activate his acount post.
I use the version 2.1.6

can sombody help me
[originally posted on jforum.net by JK]

[Migrated From Jforum.net]

Is the post being done as the Anonymous user or the unactivated user? E.g., what id shows up on the posting.

If it's anonymous, you need to remove the anonymous user from the General group and add it to a (probably new) group that can't post.

If the un-authenticated user is showing up, then it may be a configuration issue or bug. And more details will be needed.
[originally posted on jforum.net by monroe]

[Migrated From Jforum.net]

The un-authenticated user is showing up.
But I have create the user for testing the email authentication and so the user has the same ip as an authenticated user.
Is that a problem?
[originally posted on jforum.net by JK]

[Migrated From Jforum.net]

is anything wrong in this settings for the user authentication?

#############################
# SSO / User authentication
#############################
# Auhentication type: use one of the following options
#
# sso: SSO based authentication. The called class will be the one
#	specified by the key "sso.implementation", whic must be an implementation
# 	of net.jforum.sso.SSO
#
# default: Non-SSO authentication, which relies on the key 
#	"login.authenticator" to validate users. For more information, please see
#	net.jforum.sso.LoginAuthenticator and the default implementation.
authentication.type = default

# The above key will be used when "authentication.type" is set to "default"
# Can be any implementation of net.jforum.sso.LoginAuthenticator
#
# For LDAP authentication, set the value to net.jforum.sso.LDAPAuthenticator. Also,
# see the LDAP section below
login.authenticator = net.jforum.sso.DefaultLoginAuthenticator

# When using authentication.type = default, you may choose to disable
# the automatic login feature, which will prevents users to get 
# automatic logged in when they come back to the forum
auto.login.enabled = true

# The above key will be be used then "authentication.type" is set to "sso"
# The default implementation (used here) only checks if request.getRemoteUser()
# is not null. This may be enough for many situations.
sso.implementation = net.jforum.sso.RemoteUserSSO

# Special attributes used when creating a new user
# Only if auhentication.type = sso
# The attribute name to search in the session for the password.
sso.password.attribute = password

# Same as above
sso.email.attribute = email

# The default email to use if sso.email.attribute is empty
sso.default.email = sso@user

# The default password to use if sso.password.attribute is empty
sso.default.password = sso 

# Optional redirect for SSO
# If any value is set, the user will be redirected to the defined
# redict, using the following logic:
# request.getContextPath() + <sso.redirect> + returnPath);
sso.redirect = 

[originally posted on jforum.net by JK]