Swivel Secure Authentication

Swivel Secure offers a wide range of authentication factors, allowing the use of 2FA and image based authentication. To learn more, please refer to the official website.

CAS supports Swivel Secure’s TURing-image based authentication. TURing uses the PINsafe protocol to provide a One Time Code for authentication. Each image is unique for that session.

image

Configuration

Support is enabled by including the following module in the overlay:

1
2
3
4
5
<dependency>
     <groupId>org.apereo.cas</groupId>
     <artifactId>cas-server-support-swivel</artifactId>
     <version>${cas.version}</version>
</dependency>

To see the relevant list of CAS properties, please review this guide.

Logging

To enable additional logging, configure the log4j configuration file to add the following levels:

1
2
3
4
5
6
...
<AsyncLogger name="com.swiveltechnologies" level="debug" additivity="false">
    <AppenderRef ref="console"/>
    <AppenderRef ref="file"/>
</AsyncLogger>
...

Swivel SDK

Note that Swivel SDK artifacts are not published to a Maven repository. This means that you will need to download the necessary JAR files and include the in your build configuration. The SDK may be downloaded from the CAS codebase. Then, assuming the SDK is placed inside a lib directory of the WAR overlay directory, it can be referenced in the Maven build configuration as such:

1
2
3
4
5
6
7
8
9
10
11
...
<dependencies>
    <dependency>
      <groupId>com.swiveltechnoligies</groupId>
      <artifactId>pinsafe</artifactId>
      <version>1.0</version>
      <scope>system</scope>
      <systemPath>${basedir}/lib/pinsafe.client.jar</systemPath>
    </dependency>
</dependencies>
...

For Gradle, you would do something similar:

1
compile files("${projectDir}/lib/pinsafe.client.jar")