Skip to main content

OpenText xPression Administration

xPressionHome is the environmental variable that point the xPression installation directory.
xPression system is a client/server environment, where xPression client must logon to xPression server. xPression users may be authenticated in four ways:

 * Local Authentication: User is authenticated on local machine by adding user to local user list on the server. To enable local user authentication, dscsecurity.properties file is configured for properties IMPL_CLASS = com.dsc.uniarch.security.user.NTUser [for windows user] / com.dsc.uniarch.security.user.LinuxUser [for linux user] and NT_AUTH = <server-name>

 Note: LDAP Properties must be commented

 * LDAP Authentication: At the time of xPression installation wizard, installer need to place LDAP authentication credentials. These settings are kept in ldapcfg.properties file, the path for ldapcfg.properties is given in dscsecurity.properties files.

 * SiteMinder Authenticaion: It is the third party application that should be configured manually after installation.

 * User Exit Authentication: In xPression, All the user should be authenticated externally for security reason. It must connect through an external directory service provider that performs the authentication action. So, java user exit may be implemented for this purpose and the configuration should be a part of dscsecurity.properties file, creating some new property file and compiling java code. 

Comments

Post a Comment

Popular posts from this blog

Java Facades

What is Facades? A facade provides a simplified interface to a larger body of code, such as a class library. Using faces, we can make More readable library Wrapped a poorly designed collection of API in a single well - designed API Reduces dependency of outside code on inner working library Facade example on Java /* Complex parts */ class CPU { public void freeze () { ... } public void jump ( long position ) { ... } public void execute () { ... } } class HardDrive { public byte [] read ( long lba , int size ) { ... } } class Memory { public void load ( long position , byte [] data ) { ... } } /* Facade */ class ComputerFacade { private CPU processor ; private Memory ram ; private HardDrive hd ; public ComputerFacade () { this . processor = new CPU (); this . ram = new Memory (); this . hd = new HardDrive (); } public ...
Post a Comment
Read more

Android Background Operations

Background operation are very helpful, while you are needed to perform operation in the background and want to continue with other applications simultaneously. There are four ways to run background jobs: Sched ule Jobs are jobs while are about run at defined time. For example, if application cache need to be refreshed at defined time. It is used to run task asynchronously. JobS cheduler is a robust way to run background tasks. it is useful for small as well as large asynchronous tasks. In addition, there are several other facilities available to write jib scheduling tasks. It was first available in Android 5.0, (21), Android 7.0 (24) added ability to trigger job on ContentProvider change. You can register jobs by specifying their network and timing requirements. It also defer the execution as necessary to comply with Doze and App Standby restrictions. For Android 5.0, it is advised to use job scheduling only. AlarmManager is another way for scheduling, useful to post notifica...
Post a Comment
Read more