WebsydianExpress - Callback Point

SessionAfterCreate

Type

Site specific callback point implemented by the WebsydianExpress runtime.

When is the callback point called

SessionAfterCreate is called immediately after the session has been created by the initial request.

This happens before the site is loaded.

How does the callback point influence later functionality

By changing roles and folder list for the created session, the callback functions called by this callback point can have a significant impact on how the site is loaded.

Errors returned in *Returned Status are disregarded by the callback point.

Example of use

If the initial request contains information that can be used to log a user in to the session, the user/password check and the update of the session with the user information can be done here.

So if for instance the initial request URL is:

https://www.myserver/site/basicsite?WSUSER=USERNAME&WSLOGIN=PASSWORD

You can extract the username and the password from the request, and then use the APIWebServer.PasswordValidationForLogin API to check the user password combination.

If it is correct, you can use the APIServer.Session.SetUserAndUpdate API  to update the user on the session. At the same time, the roles and folder list will be updated just as if the user had logged in through the login page. This means that the login page will be bypassed.

Abstract callback function

Inherit from Callback.WebServer.SessionAfterCreate.AbstractCallbackFunction to create a callback function that can be called by this callback point.

CallbackInput

This local variable contains:

• APIFields.SessionSurrogate - The unique identification of the session that has just been created.

This field will be populated automatically by the callback function. Use the value of the field as you would use a normal input field.