Our client wanted to be able to authenticate a user to NAM from a application.
We advised that the "right(?)" method would be to use SAML, but that was a little far out for them to accomplish.
We got a lot of information on this from the NAM documentation on NAM Customized JSP Pages. Novell's documentation provides:
What we noticed was that if we first went to one of the protected resources and then posted to the idp server, that SSO did work. We then created a page with an iFrame (set so small no one would see it) that contained the login page to a "protected resource" and then posted to the page to the idp cluster with a hidden value for the target in the post. This appears to work fine.
This allowed us to obtain credentials from a source that is not available to NAM and be able to authenticate to NAM. Keep in mind that the credentials must match those in NAM's userstore to work.
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>NAM Posted Login</title> </head> <body bgcolor="white"> <form name="login" id="login" method="post" action='https://idp.yourdomain.com:8443/nidp/app/login' > <table border="0" cellspacing="5"> <tr> <th align="right">Username:</th> <td align="left"><input type="text" name="Ecom_User_ID"></td> </tr> <tr> <th align="right">Password:</th> <td align="left"><input type="password" name="Ecom_Password"></td> </tr> <tr> <td align="right"><input type="submit" value="Log In"></td> <td align="left"><input type="reset"></td> </tr> </table> </form> </html>