nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Non-OS User Management

ReggieRWalker

Env: TS 6.7.1 SP1 / RedHat 4

I'm trying to create a Non-OS user. When I click "Add User," the Database dropdown is greyed out with OS as the value. I checked another Win2K3 server and got the same results. Is there some configuration setting I forgot or is this another SP bug?

Find more posts tagged with

Comments

CRB

i have the same issue, but i havent had time to read the manuals yet..
i think you need to do some configurations in the userdatabase xml file. and i am not sure yet, but i think you need LDAP to create non OS users... i also dont know if the LDAP comes with the SP1 or if we have to install our own if the company doesnt use it... i hope somebody could answer those questions for me till i get time to read the manuals.

TS 6.7.1 SP1 W2003 SP1

ReggieRWalker

According to Support, you are correct although I don't think most of us interpreted "Non OS" user that way. This is the response I got back from IWOV:

**********************************************************
“TeamSite Master users can add non-OS users to TeamSite without waiting for the IT department to add these users to the operating system.”

Prior to 6.7.1 SP1 If the Master user has to add any user to TeamSite he has to request for IT department to add this user firstly to OS.

Now in SP1 TeamSite Master users can add non-OS users to TeamSite without waiting for the IT department to add these users to the operating system. It doesn't say that it won't require IT help but it says that you can add non-OS users without waiting for the IT dept. to add them to the OS.

As per the non-os is concerned the purpose was to separate TeamSite from a reliance on local OS users and/or domain users.

you can set up a totally separate LDAP server, which the TS admins can control completely. It doesn't have to be a corporate LDAP server that all departments use.
**********************************************************

I don't know about your organization, but I don't know very many that would allow any non-IT personnel to have much access to any LDAP server or database! :-( I think this feature is misleading (as usual).

HTH

Adam Stoller

According to Support, you are correct although I don't think most of us interpreted "Non OS" user that way. This is the response I got back from IWOV:

**********************************************************
“TeamSite Master users can add non-OS users to TeamSite without waiting for the IT department to add these users to the operating system.”

Prior to 6.7.1 SP1 If the Master user has to add any user to TeamSite he has to request for IT department to add this user firstly to OS.

Now in SP1 TeamSite Master users can add non-OS users to TeamSite without waiting for the IT department to add these users to the operating system. It doesn't say that it won't require IT help but it says that you can add non-OS users without waiting for the IT dept. to add them to the OS.

As per the non-os is concerned the purpose was to separate TeamSite from a reliance on local OS users and/or domain users.

you can set up a totally separate LDAP server, which the TS admins can control completely. It doesn't have to be a corporate LDAP server that all departments use.
**********************************************************

I don't know about your organization, but I don't know very many that would allow any non-IT personnel to have much access to any LDAP server or database! :-( I think this feature is misleading (as usual).

HTH

I won't argue the points you made - because frankly I agree with them as far as they go - however, there's one aspect of this which you didn't cover...

One of the primary reasons for supporting LDAP-only accounts, as I understood it from the presentation at GearUp this past May, was to aid in the support of single-sign-on functionality so that once a user is authenticated to the corporate LDAP server they would also be authenticated to TeamSite (or so it sounds anyway).

Unfortunately (IMO) - that feature comes with costs - in that you can no longer rely on user impersonation at the file system level because the accounts don't exist at that level, and thus any Perl code that was written which took advantage (knowingly or not) of the impersonation functionality will need to be re-written; not the least of which is the entire PT processing system - which is built in Perl .. instead of using your existing PTs with iwpt_compile.ipl and/or iwgen / iwregen - you have to write XSLT and use the new XSLT PT system (I haven't had a chance to play with any of this yet - this is all based on conversations held during GearUp)

So - I think the "bang" one might get for this "buck" will vary greatly depending on the needs of the organization. I have a feeling that there will be a few early-adopters who have been chomping at the bit for this ability, but that a large percentage of the existing customer base will probably continue to use OS-accounts.

Antharix

Well, Does non-OS users mean LDAP/ AD users? Or is this some kind of users that could be created on teamsite ( user that is not a part of the OS or AD).

Clarification will be highly appriciated.

Adam Stoller

Well, Does non-OS users mean LDAP/ AD users? Or is this some kind of users that could be created on teamsite ( user that is not a part of the OS or AD).

Clarification will be highly appriciated.

It means LDAP account.

smenon

Let me clarify a couple of things here..

1) TeamSite is not looking to be in the business of being a native user repository including managing user passwords etc. Hence, the approach we took was to allow customers to use any standard LDAP compliant user repository as the source repository for user accounts.
2) The value of non-OS users is greater for those customers that need to jump through hoops to setup and create user accounts - especially when the users require network access. Of course, this requires that you have access to an LDAP compliant repository. If you dont have access to your corporate LDAP/AD server, then you can setup an instance specifically for TeamSite if you have the option to do so. Alternatively, you can use the URL interface based non-OS user management. If you setup your own user management application (say on top of a database or a filesystem), and you implemented the interfaces we expose for user management, TeamSite will call your application by looking at the external user source configuration information in /conf/roles/. There should be an example file and configuration in the examples directory there.

Are there things you need to do to leverage non-OS users? Yes - absolutely, but there are certain customers where the pain to setup users is so high that they are willing to perform these extra steps such as using URL External Tasks, XSLT based presentation templates etc in order to not have to rely on the core system IT resources for user management. You can always take an evolutionary approach where you can start leveraging non-OS users for new websites/branches you are setting up and then slowly over time migrate all of your users from OS to non-OS users.

I hope this helps..

thanks

ISCBorisB

Sunil, are you planning to participate in NY User Group meeting on 9th?

smenon

Unfortunately not.. I attend User Groups mostly by invitation since the User Groups are run by customers/users, unless there is a topic that requires me to attend.

Was there something specific you were looking for? Send me an email and we can discuss.

ISCBorisB

Unfortunately not.. I attend User Groups mostly by invitation since the User Groups are run by customers/users, unless there is a topic that requires me to attend.

Was there something specific you were looking for? Send me an email and we can discuss.

Thanks, will do