Filtered Index

There are several reasons that cause the NAM to detect URL Tampering. Most often it is a name resolution issue stemming from improper DNS or HOSTS file configuration in your environment. Still, even with proper configuration your users may, appropriately, get this message. The reason may stem from users having become accustomed to using web server host or “short names” to access the web server/app before it was protected by Access Manager. If that is the case, this article will show you when and how you can configure NAM to allow “short name” access using the Virtual Mult-homing feature.

Updated with a version for Access Manager 3.1.2.
The ability to single sign on (SSO) to NetIdentity aware Web applications was available with Novell's iChain product. Novell Access Manager, the successor to the iChain product, does not include any NetIdentity authentication profile or class. The attached jar file offers the ability to SSO to Access Manager from NetIdentity enabled workstations. This document describes the requirements and configuration steps required to get NetIdentity SSO to Access Manager, and describes the NetIdentity protocol exchange during authentication.

This is a short article providing an easy, but perhaps a not so obvious way, to use Novell Access Manager (NAM) for Single Sign-On (SSO) access to the Oracle E-Business Suite (OEBS). OEBS is used as the example, but the same SSO enabling strategy used here can be applied to other web applications as well.

This is an updated article on how to use Novell Access Manager 3.1.1 to provide Single Sign On with IDM UserApp 3.6.1. It also discusses how to setup the expired password handling in NAM to redirect to the UserApp Change Password feature.

Single Sign-on by using Formfill with Autosubmit enabled fails if the submit or the login button requires execution of a JavaScript function before submitting the form data to the Web server. The classic example for such forms is HP Service Manager login form. Here's a solution from Jency Flawrence and Sahana Mathias.

Using Novell Access Manager (NAM) with salesforce.com allows your users to use their existing LDAP credentials for single sign-on access to salesforce.com as well as any web applications protected by NAM.

This cool solution will show you how to add salesforce.com to your NAM implementation using a federated authentication via SAML 2.0. By using SAML 2.0, your users authenticate to NAM as they typically do using their existing LDAP credentials provided by your corporate directory. salesforce.com then authenticates users via SAML without the need to synchronize passwords with salesforce.com. Once configured, your users will have SSO access to all your web resources protected by NAM through either the Access Gateway or using federation protocols. Unfortunately, salesforce.com does not support federated provisioning, so you will still need create users in salesforce.com. If you would like to automatically provision, deprovision, and manage the salesforce.com identities, you can use Novell Identity Manager, but that is out of scope for this article.