IBM Support

Using Third-Party Classes in an ISAM AAC Custom Authentication Mechanism/Obligation

Troubleshooting


Problem

When the built in Authentication Mechanisms or Obligations do not supply the needed functionality one can build a custom authentication mechanism to fill the gaps. If the JAR's MANIFEST is not properly constructed it can lead to class not found exceptions and unwanted behavior when running the authentication mechanism.

Symptom

The browser will show :

java.lang.NoClassDefFoundError: <class-in-question>
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:346)

Example :

java.lang.NoClassDefFoundError: org.apache.http.HttpMessage
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:346)

[{"Product":{"code":"SSELE6","label":"IBM Security Access Manager for Mobile"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Documentation","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
16 June 2018

UID

swg21995250

Page Feedback