Changes to pages, redirects and userlevels.

I have found that the only safe method of making any changes to pages made with this script is to delete all of them and start over. That can mean a lot of work, as all your existing changes to pages that are working OK are lost.
It would be far better if each page could be created by itself. That way, the only work that could be lost would be on that one page.
I have a major problem in that while I have managed to get the registration page to direct to the login page on a successful registration, I cannot get the login page to direct to any page other than the login failed page.

Can anyone tell me where in the system it is possible to tell the login page to go to one page if it is successful, and to another if it is unsuccessful, other than modifying the raw code by hand.

Also, I have a table in my system that has a list of defined groups. I can see no way of integratingthis into the WA system. I don't wish to be adding groups by hand if the system does get up and running. All that should be required once the pages are set up, is to add a group to the group list in the database and tell the relevant pages that this group has access rights.
Is this possible in SA?

The documentation on the web site is for SA 1X (unless anyone knows better).
Will there be any for 2X, and if so, when?

Videos are an unsuitable form of documentation to give anything other than a brief insight into any problem..

To set the login redirect for success and failure, you will need to edit the Security Assist Authenticate user server behaviors. Open the server behavior panel on the login page, then double click the Security Assist authenticate user behavior to modify it.

you will have options for setting the success and failure redirect urls.

to set user level access in security assist, you need to create an access rule for each group. simply adding the group to the database does not tell security assist what that group can or cannot access.

you need to create the access rules for your site to use those groups.

The User level authentication tutorial that was written for security assist 1 is still relevant in security assist 2, the process is still the same.

I dont have a time frame for when more documentation specific to security assist 2 will be created, but if there is some thing specific you need help with, please feel free to post the question here.

if there is specific documentation you would like to see created, please submit your feature request to the wishlist forum.

Now that I know where to access the server behaviours, life becomes a lot easier.

With regard to groups, I have used these before in ASP, and when a member logs in, a session variable is set holding the group he belongs to. This information is pulled from the database. When he tries to access the page, the page checks the session group variable to see if this group is allowed to enter the page and if it matches, lets him in or sends him elswhere.

In order to allow users to belong to groups, surely the group that a member belongs to must be stored in the database. If you have to tell SA which group each member belongs to, you could be typing for years. I have 28,000 members on my site. Apart from about 60 or so, which need to be individually grouped, the rest are automatically put into the default groups by the default value created by the MySQL database on registering.

How exactly does the group thing work?

yes the groups need to belong in the database.


you users table should have a column that sets what group they belong to.


in the authenticate user behavior, go to the third step, you can select columns from your table that will be stored in a session, select the groups column so that the group will be stored in a session at login time.


you then have to configure the access rules for each group to compare the session that contains the users group

this is all covered in the user level authentication tutorial on the security assist support page, like i said perviously, it was written for SA1, but the concepts are identical in SA2.