Hello,
I'm working on implementing SSO using 4D Server's new feature for that in
our Windows environment. I'm working with our corp AD security folks and
haven't got it to work yet (lots of hoops to jump through), but am trying
to figure out how it works in the absence of being able to try and
Bob,
The whole idea with Single Sign On is that the user logs in to the machine, and
then subsequent system they use while logged in to the machine will use the
same login credentials automatically.
So with your situation of User A being logged in to the machine, but User B
wants to use the 4D
RE> User A should not be sharing the machine with User B, otherwise, if
they are sharing, then SSO should not be used.
OK, I accept that.
In a different view of things (this wouldn't be SSO, but rather, using AD
authentication) there some way that I could present a login screen, accept
the us
> In a different view of things (this wouldn't be SSO, but rather, using AD
> authentication) there some way that I could present a login screen, accept
> the user's ID and password, and send it to AD for authentication, receiving
> back a "Good" or "Bad" reply?
Based on this, I think you want
Timothy Penner mailto:tpen...@4d.com>> responded to Bob Miller
mailto:bob.mil...@parker.com>>
>The whole idea with Single Sign On is that the user logs in to the machine,
>and then subsequent system
>they use while logged in to the machine will use the same login credentials
>automatically.
5 matches
Mail list logo