Anonymous_User Absent Member.
Absent Member.
790 views

Random corruption of user's NSL7 credentials


We are planning on migrating our NSL 3.5.1 / eDirectory estate to NSL
7.0.3 SP3 HF2 /AD and I am currently developing/tweaking the application
scripts in the new environment before trialing the product at a couple
of beta sites (we have 10,000+ users of NSL)

The dev environment is fairly simple, with just 2 Windows 2003 DCs, and
a couple of Windows XP workstations.

During my testing I have noticed a couple of occassions where my test
user's NSL credentials have become corrupted such that I end up with two
or more 'logins' for a single application on their user object (only 1
of which contains real information, the others just have the default
username/password fields which are blank). When I then start the
application, I am prompted by NSL to select which set of credentials I
want to use.

I have never seen this sort of thing before in the NSL 3.5.1 /
eDirectory world, so am unsure what could be causing this now. Is it
something going wrong with NSL 7, or perhaps AD ? I can't see any errors
in the event log on the PC which might indicate something has gone
wrong.

Perhaps it's related to my use of 'SLManager' on one of the DCs to
update applications/check the user account whilst the test user is
logged in on the XP workstation ? I am shocked as to how awful the
'SLManager' application is from a useability point of view, so I am
thinking it's not impossible for it to be the source of the corruption.

Has anyone seen any problems with random NSL credential
corruption/duplication and identified any possible causes ?


--
clovercne
------------------------------------------------------------------------
clovercne's Profile: https://forums.netiq.com/member.php?userid=1699
View this thread: https://forums.netiq.com/showthread.php?t=3027

0 Likes
6 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Random corruption of user's NSL7 credentials

clovercne,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://forums.novell.com/

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Random corruption of user's NSL7 credentials


I saw this quote from David on another thread:

-"In the NSL preferences have you got the "*Detect Incorrect Passwords*"
set
to Yes. This makes NSL watch any scripts that are running and sees if
they are being initiated too many times in a set period. If they are
then it assumes that the password is wrong and asks for all of the
variables to be re-entered."-

It's not entirely what we are seeing, but it might be related. I have
looked for this setting in preferences to turn it off, but I can't find
it !

Does it still exist in NSL 7.0.3 ?


--
clovercne
------------------------------------------------------------------------
clovercne's Profile: https://forums.netiq.com/member.php?userid=1699
View this thread: https://forums.netiq.com/showthread.php?t=3027

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Random corruption of user's NSL7 credentials

The location to set the "Detect Incorrect Passwords" is in the
Preferences/General section of the client.

Dave

On 16/10/2012 12:24, clovercne wrote:
>
> I saw this quote from David on another thread:
>
> -"In the NSL preferences have you got the "*Detect Incorrect Passwords*"
> set
> to Yes. This makes NSL watch any scripts that are running and sees if
> they are being initiated too many times in a set period. If they are
> then it assumes that the password is wrong and asks for all of the
> variables to be re-entered."-
>
> It's not entirely what we are seeing, but it might be related. I have
> looked for this setting in preferences to turn it off, but I can't find
> it !
>
> Does it still exist in NSL 7.0.3 ?
>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Random corruption of user's NSL7 credentials


Yeah that's where I was looking. It's not there though!!

We are running NSL 7 SP3 HF2 in native AD mode if that's any help...


--
clovercne
------------------------------------------------------------------------
clovercne's Profile: https://forums.netiq.com/member.php?userid=1699
View this thread: https://forums.netiq.com/showthread.php?t=3027

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Random corruption of user's NSL7 credentials


same config, not having that setting either.


--
florianz
------------------------------------------------------------------------
florianz's Profile: https://forums.netiq.com/member.php?userid=309
View this thread: https://forums.netiq.com/showthread.php?t=3027

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Random corruption of user's NSL7 credentials


Its seems to be an issue on the SP3 version.

All my SP2 setups have this option and none of the SP3 doesn´t.


--
z3maf
------------------------------------------------------------------------
z3maf's Profile: https://forums.netiq.com/member.php?userid=307
View this thread: https://forums.netiq.com/showthread.php?t=3027

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.