Home > Novell Error > Novell Error 16049

Novell Error 16049

We provide identity and access management, single sign-on (SSO), access governance, and more. Depending on the Unix variant (AIX, HPUX, Solaris, or Linux family) the implementation is slightly different. Learn more about Security Management Solution Brief: Identity Powered Security Detect and disrupt security threats quickly Get compliant, stay compliant Configure systems to protect against threats Protect sensitive data Monitor the User with no Simple Password at all: java -jar DumpPasswordInformation.jar -h 10.1.1.91 -Z SSL -p 636 -D cn=admin,ou=admins,o=acme -e MyKeyStore -w password -b "cn=tuser2,ou=Migrated,dc=acme,dc=corp" # dn: cn=tuser2,ou=Migrated,dc=acme,dc=corp Password: acme1234 Password Policy weblink

The time now is 11:48 PM. © 2016 Micro Focus NetIQ Forums > PRODUCT DISCUSSION FORUMS > IDENTITY & ACCESS MANAGEMENT > eDirectory > Modular Authentication Services & Universal Password > The other is called the Fanout Driver, to handle the case when you have hundreds to thousands of Unix machines that need to be managed. It's best to do it to a container, AFAIK. 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share Loading...

SSL (actually TLS), the proxy user, the search context, the search for the user, and the bind attempt. It also turns out that there is an excellent driver for Novell Identity Manager that will synchronize users to and from NIS, NIS+, or even files on Unix machines. For example try a CIFS login to test UP. But I know that my Password Policy in this tree says to synchronize the Universal Password to Simple Password and to NDS password.

  1. So what tools do we have?
  2. I was trying to copy a production environment into an isolated lab environment for testing so this was ok. 601 error, no such user: java -jar DumpPasswordInformation.jar -h 10.1.1.10 -Z SSL
  3. Try a Client32 bind with NMAS to test UP as well, then try on a client with NMAS installed.
  4. Lets focus on Linux for now though, since each traditional Unix is sufficiently different to need its own explanation.
  5. Join the community of 500,000 technology professionals and ask your questions.
  6. The eDirectory tools which manage policy assignments currently create both attributes properly and do not allow doing one without the other.It is possible that an administrative error could cause one of
  7. To follow along with this video, you can draw your own shapes or download the file… Illustration Software Photos / Graphics Software Web Graphics Software Adobe Creative Suite CS How to
  8. It can specify for a variety of services which modules to use.
  9. Password: null Password Policy for Entry: cn=All Users Policy,cn=Password Policies,cn=Security Does Current password meet password policy assigned to user?

true ===> Password Status <=== ==> Universal Password <== Is UPwd Enabled: true Is the UPwd history full: false Does UPwd match NDSPwd: true Does UPwd match SimplePwd: true Is UPwd All rights reserved. CONTINUE READING Suggested Solutions Title # Comments Views Activity Novell Login Lag 1 567 1576d Novell OES Admin password not recognised 8 363 923d Novell time synchronisation 7 306 921d Xenapp Document ID:3537706Creation Date:04-JUN-07Modified Date:26-APR-12NovellNMAS (Modular Authentication Service)NetIQeDirectoryIdentity Manager Did this document solve your problem?

Environment Novell Modular Authentication Service (NMAS) version 3.1 Situation When trying to view a user's password policy via iManager or trying to set the Universal Password (UP) via iManager, the client, This was a reversible version of your password, and they introduced a whole slew of bits and pieces needed to make this all work. No keys were valid. Comment Cancel You must be logged in to post a comment.

Password policy is working and being enforced! With just that one password, CIFS, AFP, and NFS logins are a piece of cake. You need to enable a password policy, that specifically enables Admin to retrieve passwords, and in the later versions of NMAS (Novell Modular Authentication Services, one of those bits and pieces By monitoring user activities, security events, and critical systems, we provide actionable security intelligence to reduce the risk of data breach.

SDI is very similar to PKI, except it has one major feature, which is old keys can remain around, but revoked. Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. In this case, I had backed up a tree from production, using Dsrepair's archive function, and restored it with the -$DU switch (Read more about this potentially astonishingly dangerous operation, if Imagine how much space that would have taken up a decade ago!

Novell's solution at the time was to use Simple Password. have a peek at these guys Removing the association between the password policy and re-adding it will resolve this. I wanted to try and show some examples of what the output should look like in various cases, and explain some of the errors you might get, when using it. A further twist was the addition of more functionality into the next version of NIS, called NIS+ (NIS plus).

DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. This also nicely confirmed that I had the password correct. Then, we will analyze the reaso… Oracle Database Gain high ROI & low CPA with some notable Digital Marketing Strategies Article by: Shakshi Digital marketing agencies have encountered both the opportunities check over here For support information, please visit Support.

For example, Unix systems can authenticate against a number of different systems. So I tried again with NMAS tracing enabled in DStrace, and look what I saw as the bind with a bad password happened: 13:03:28 B72EBBA0 NMAS: 43: Create NMAS Session 13:03:28 NMAS error codes A side tip, if you are searching for error codes, you need to include the minus sign.

I exported via LDIF all the passwords from production, then imported into the lab, then I burned the file!). (0 votes, average: 0.00 out of 5)You need to be a registered

But once you are past those hurdles, it works very well. Jun 3 09:36:12 and601lnx sshd[13421]: Invalid user jsmith from 10.1.1.10 Jun 3 09:36:20 and601lnx sshd[13423]: pam_ldap: error trying to bind as user "cn=jsmith,ou=Migrated,dc=americas,dc=acme,dc=corp" (Invalid credentials) Jun 3 09:36:20 and601lnx sshd[13421]: error: The solution was then to add the posixAccount value to the Object Class attribute of all the users. Does the server object have the appropriate rights?

The pam module of choice that I find most compelling is pam_ldap. Then there is NFS which sometimes uses MD4 (or is it MD5, whatever, it is the other one from LANMAN). As long as nspmPasswordPolicyDN is populated everything should work properly but if nsimAssignments is the only attribute populated a -16049 error will appear because the attribute which is sought cannot be this content Simple Password did not last long, as it too had limitations, and work was underway to get to a better solution.

Click the LOGIN link in the forum header to proceed. Universal password not set?', > > When the user fails to authenticate, I just see: > > Fri Oct 6 09:11:15 2006: DEBUG: Radius::AuthLDAP2 looks for match > with > xxxx This is just an annoyance really, once you understand it. Sales:1-800-796-3700 Support:1-800-858-4000 Connect with us Feedback Form We adapt, you succeed.

Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS Home Skip This is of course by design. I used Console One with the NMAS snapins, but the iManager NMAS snapins can do this as well. true ===> Password Status <=== ==> Universal Password <== Is UPwd Enabled: true Is the UPwd history full: false Does UPwd match NDSPwd: false Does UPwd match SimplePwd: false Is UPwd

Crazy that a missing unneeded auxiliary class on a user object was the root cause, and looked like a Simple Password login problem, but that seems to have really been it! First off, I told pam_ldap to use the ldapibm account to search as, and that it succeeded and was able to find my jsmith user. 13:03:28 8175DBA0 LDAP: (10.1.1.10:42942)(0x0002:0x60) DoBind on But please be sure to test, test, test before you do anything drastic with it. I had only granted the ldapibm user a limited set of rights. 13:14:00 B5FD8BA0 LDAP: New cleartext connection 0xa39da00 from 10.1.1.10:47546, monitor = 0xb63dcba0, index = 113 13:14:00 B68E1BA0 LDAP: (10.1.1.10:47546)(0x0003:0x63)

Connect with top rated Experts 18 Experts available now in Live! For CIFS, just hash the password stored, compare, good to go. Finally I gave up and opened an incident with Novell, since I know this works, and clearly something was goofy. Well from a pure security perspective, you betcha.

You can read more about it in this article Auxiliary Classes and Identity Manager but the gist of it is, that IDM will add any needed auxiliary classes that are needed, Service & Univ. Thanks. 0 Question by:wpcpa Facebook Twitter LinkedIn Google LVL 35 Active 2 days ago Best Solution byShineOn https://secure-support.novell.com/KanisaPlatform/Publishing/805/3629717_f.SAL_Public.html TID 3629717 sounds like it fits your issue. I suppose I could have contrived a case where I had a UP password, a different Simple Password, and a different NDS password.