To make this possible, NextReports defines a process which first brings the users into the content repository. A simple xml configuration will define synchronization process. You must specify your data source and your queries to get users names and users attributes (which allows to map any fields you may have to NextServer repository):
<bean id="syncService" class="com.asf.nextserver.security.DatabaseExternalUsersService">To define your CAS , a validation ticket must be written which will inform about cas login and cas logout urls:
<property name="dataSource" ref="syncDataSource"/>
<property name="userNamesQuery">
<value>SELECT USER_NAME FROM USERS</value>
</property>
<property name="userQuery">
<value>SELECT * FROM USERS WHERE USER_NAME = ?</value>
</property>
<property name="mapping">
<map>
<!-- required -->
<entry key="user.username" value="USER_NAME"/>
.......
</map>
</property>
</bean>
<bean id="tValidator" class="com.asf.nextserver.web.security.cas.CasServiceTicketValidator">
<constructor-arg index="0" value="https://myurl:myport/cas"/>
<property name="loginUrl" value="https://myurl:myport/cas/login"/>
<property name="logoutUrl" value="https://myurl:myport/cas/logout"/>
</bean>
Hi can you show how to make CAS work with LDAP (AD) ? thanks a lot
ReplyDelete