ca.portal.admin

Re: Common Signon

Discussion created by ca.portal.admin on Feb 28, 2006
When you say ""they have to signon to each cv"", where are these
users=0D=0Ac= oming from? TSO? CICS? VTAM?=0D=0A=0D=0ALutz
Petzold=0D=0A=0D=0A=0D=0A=
=0D=0A=0D=0A-----------------------------------------=0D=0AThis e-mail
may = contain confidential or privileged information=2E If
you=0D=0Athink you ha= ve received this e-mail in error, please advise
the sender=0D=0Aby=0D=0Arep= ly e-mail and then delete this e-mail
immediately=2E Thank you=2E=0D=0AAet= na=0D=0A

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] Common Signon
"BUT BUT BUT.....the node isn't checked until the program does a bind
run-unit. This makes the db run-unit run over at the other cv, but not
the application. I think Dan wanted the application to run on their own
cvs too.

Lutz Petzold




-----------------------------------------
This e-mail may contain confidential or privileged information. If you
think you have received this e-mail in error, please advise the sender
by
reply e-mail and then delete this e-mail immediately. Thank you.
Aetna


"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: Common Signon
"Dan,

It is relatively simple. All you need to do is make an SGON entry in
the SECRTT stating that signon is external and make sure that the id
used externally matches the id used by the CV so that when the user
passes from external to the CV all the IDMS security allows them to do
what they want to.

If everybody has the same id in all the different CVs, then just set up
the external signon to use that same id, modify the SECRTT and
everything should work flawlessly.

Danbury was the first place where I had to sign on to a CV in several
years of consulting.

John Wheeler

Outcomes