anitone Absent Member.
Absent Member.

SecureLogin decommissioning

We are decommissioning SecureLoign. The Client has been removed from all
workstations. Now what do we have to do to remove SecureLogin 'from the
server' so we are not using any licenses any more (also for the Novell
licensing check) and decommission permanently ? Is this a case where the
SecureLogin attributes have to be manually removed from all user
accounts which have them?

Thanks for any information provided.

anitone's Profile:
View this thread:

3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: SecureLogin decommissioning


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 issue been resolved? If not, you might try one of the following options:

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

Be sure to read the forum FAQ about what to expect in the way of responses:

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 NetIQ Forums Team

florianz1 Absent Member.
Absent Member.

Re: SecureLogin decommissioning

i am not familiar with necessities regarding cleaning up attributes, but
you could do that. depending what your server base is, edirectory or AD,
you then should be able to get rid of the attributes itself.
eDirectory, to my knowledge, allows to remove classes and attributes
from the schema if no object any longer uses them. AD does not, but lets
you set those 'defunct'.

i would delete all stored data for reducing the databses size in any
case. you could use slaptool or a ldif to achieve that.


florianz's Profile:
View this thread:

tdrewry Absent Member.
Absent Member.

Re: SecureLogin decommissioning

Each user object in the directory that contained SecureLogin data will have "prot..." Schema extensions. You will need to remove the data from the "prot... Entries" object to pass any licensing audit. Note that I would recommend removing all data from all of the "prot..." Objects just to clean it all up.


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.