KB221025: How to Use an External Security Module to Redirect to an External Custom Page after Users Log in using the MicroStrategy Web SDK

By default, users will be directed to the Desktop page after logging in. Developers may want users to be redirected to a custom page after logging in.
This behavior can be modified in an ESM as follows:

• Override the handlesAuthenticationRequest() method, to return COLLECT_SESSION_NOW
• Override getWebIServerSession() to retrieve user's credentials and create a session
• Create a variable, for example "redirect", and set that to true once the session is created in the getWebIServerSession()
• Override isRequestAuthorized(), which is called with every request. In this method, check if the redirect variable is true. If it is, return false, which will call the getFailureURL() method. Otherwise, return super().
• In the getFailureURL() method, return the desired url.

 

package com.Strategy.sdk.esm;

import com.Strategy.utils.serialization.EnumWebPersistableState;
import com.Strategy.web.app.AbstractExternalSecurity;
import com.Strategy.web.app.ExternalSecurity;
import com.Strategy.web.app.LoginForm;
import com.Strategy.web.beans.RequestKeys;
import com.Strategy.web.objects.WebIServerSession;
import com.Strategy.web.objects.WebObjectsException;
import com.Strategy.web.objects.WebObjectsFactory;
import com.Strategy.web.platform.ContainerServices;
import com.Strategy.webapi.EnumDSSXMLAuthModes;

public class ESMRedirectAfterLogin extends AbstractExternalSecurity {

	 private String sessionState;
	 private boolean redirect = false;

	
	@Override
	public int handlesAuthenticationRequest(RequestKeys reqKeys,
			ContainerServices cntSvcs, int reason) {
		// TODO Auto-generated method stub
		System.out.println("Method called: handlesAuthenticationRequest\t reason="+reason);
		return COLLECT_SESSION_NOW;
	}
	
	
	public WebIServerSession getWebIServerSession(RequestKeys reqKeys,
			ContainerServices cntSvcs) {
		//return super.getWebIServerSession(reqKeys, cntSvcs);
		
		System.out.println("Method Call: getWebIServerSession called");
		WebIServerSession isess = null;		
		isess = WebObjectsFactory.getInstance().getIServerSession();		 
		isess.setServerName("servername");		 
		isess.setAuthMode(EnumDSSXMLAuthModes.DssXmlAuthStandard);		 
		isess.setServerPort(0);		 
		isess.setProjectName("Strategy Tutorial");		 
		isess.setLogin("administrator");		 
		isess.setPassword("");

		try {
	            isess.getSessionID();
	            sessionState = isess.saveState(EnumWebPersistableState.MAXIMAL_STATE_INFO);
	            redirect = true;
	            System.out.println("Session successfully created and saved!");
	            
	            //return false; // force getFailureURL to be called
	        } catch (WebObjectsException e) {
	            System.out.println("Session could not be created!");
	            e.printStackTrace();
	        }

		//return true;
		return isess;
	}
	
	@Override
	public boolean isRequestAuthorized(RequestKeys reqKeys,
			ContainerServices cntSvcs, WebIServerSession user) {
		// TODO Auto-generated method stub
		System.out.println("Method called: isRequestAuthorized");

		if(redirect){
			return false;
		}
		return super.isRequestAuthorized(reqKeys, cntSvcs, user);
	}
	
	
	public String getFailureURL(int reqType, ContainerServices cntrSvcs) {
        System.out.println("Method called: getFailureURL");
        if (redirect) {
        	if(reqType==ExternalSecurity.AUTHORIZATION_REQUEST){
        		return "http://www.Strategy.com";
                //return "mstrWeb?evt=2001&src=mstrWeb.2001&systemFolder=7&mstrSmgr="+sessionState;
        	}
        } 
        else {
            return super.getFailureURL(reqType, cntrSvcs);
        }
    }

	
}

 
 
The example provided in this document is provided “as-is” to the user and assumes that the user:

• Can program, compile (e.g. javac, jikes, etc.), and execute Java programs
• Can configure environment variables (e.g. JAR files, property files, etc.)
• Have all the necessary tools to create Java applications (JDK, IDE, etc.)
• Has access to the Strategy SDK documentation.
• Has read the customization warning at the bottom of this document

 
PREREQUISITES:
For the sample to work, the Strategy Web JAR files must be accessible by the Java Runtime
Environment. The Strategy Web JAR files can be found under:

• Strategy Web Universal (JSP): {web_root}/WEB-INF/lib directory.
• Strategy Web (.NET): Program Files\Common Files\Strategy directory.

 
Note:
More elaborate programs will require additional library files and are out of the scope of this document.
 
ADDITIONAL INFORMATION:
The Strategy SDK allows you to customize the standard Strategy Web interface, and extend and integrate the Strategy business intelligence functionality into other applications. However, before changing the way Strategy Web products look or behave, it is helpful to understand how the application is built. For more information regarding the Strategy Web architecture or the process of customizing Strategy Web, please refer to Strategy Developer Zone (https://community.strategy.com/topic/0TO44000000FliLGAS/sdk).
 
To access the Strategy Developer Zone, you must have access to the Strategy Knowledge Base, you must have purchased the Strategy SDK, and you must be current on your Strategy maintenance agreement. If you are a US-based business and believe that you satisfy all three of these conditions but you do not have access to the Strategy Developer Zone, please contact Strategy Technical Support at support@microstrategy.com or at (703) 848-8700. If you are an international business, please contact Strategy Technical Support at the appropriate email address or phone number found at https://www.microstrategy.com/en/support/contact-support.
 
 
CUSTOMIZATION WARNING:
This customization is provided as a convenience to Strategy users and is only directly applicable to the version stated. While this code may apply to other releases directly, Strategy Technical Support makes no guarantees that the code provided will apply to any future or previous builds. In the event of a code change in future builds, Strategy Technical Support makes no guarantee that an updated version of this particular customization will be provided. In the event of a code change in future builds, Strategy may not be able to provide additional code on this matter even though this customization is provided at this time for this specific build. For enhancements to this customization or to incorporate similar functionality into other versions, contact your Account Executive to inquire about Strategy Consulting assistance.