iwidmap error while using iwguser

We have new TS 74.1 installed and local accounts for iwguser, iwts created by installer. When we are running iwidmap to map all non-OS accounts to iwts - we dont see any error. But when I try to idmap to iwguser, we get an error saying "Error finding id for user = iwguser". Should we not use iwguser for running idmap? Or am I missing something?

Find more posts tagged with

Comments

Rick Poulin

You're probably missing something, as mapping a user to iwguser doesn't make any sense.

The error is saying that iwguser is not a valid teamsite user, as opposed to saying it's not a valid OS user. But you wouldn't want iwguser to be a teamsite user anyway, as it's not a user that anybody uses as their login -- it's a different concept altogether.

Adam Stoller

To follow up on rpoulin's posting - iwguser is used internally be TeamSite to map Non-OS users to an entity that the OS can recognize - similar to the way TeamSite groups are mapped to iwglobal. You should not attempt to use either of those entities (iwguser or iwglobal) directly.

ts_tech

Thanks for your reply. To give a background : We are bringing in bunch of users from our existing system 672 ( solaris local OS account users) to an AD managed 741 (linux - non OS setup). We dont want users to have OS access, but remain as tsuser through LDAP authentication. As a best practice, what would you map non-OS users to in this type of scenario?

Rick Poulin

You still map them to their LDAP user ID, as that's how TeamSite will identify them whether your user datasource is set up as OS users or not.

Adam Stoller

Thanks for your reply. To give a background : We are bringing in bunch of users from our existing system 672 ( solaris local OS account users) to an AD managed 741 (linux - non OS setup). We dont want users to have OS access, but remain as tsuser through LDAP authentication. As a best practice, what would you map non-OS users to in this type of scenario?

rpoulin already gave you the answer - but I'll ask a few more questions:

If the answer to any of these questions is "yes" - you need to fix that before you convert your users to Non-OS users.

ts_tech

We are not using ui customizations through perl. They exist on an external tomcat java app, which goes through a http call from our serlvet. And no PTs.