Techniques for keeping logins and password synchronised between two dataservers

[robert]

Sybase ASE 12.5.4

As per the subject, I'l looking for a way where creating a login or
changing it's password on dataserver A also happens on dataserver B,
and vice-versa.

Would it be possible to replace master..syslogins on B with a
proxy_table pointing to A? I've tried it but could not drop local
syslogins (would probably cause havoc anyway).

Any other suggestions?

[Rob V [ Sybase ]]

ASE 15.0.1 or later allows you to replicate invocations of sp_password. With
Replication Server (any RS version beyond RS 12.0) you can then configure
the master database for replication and consequently when a password is
changed, this change will be replicated to the syslogins tables of other the
ASE servers that are the replication targets.
Without replication, the classic workaround is to modify the stored procs
sp_password and sp_addlogin to call the corresponding procedures in the
remote ASE servers as RPCs

HTH,

Rob V.
-----------------------------------------------------------------
Rob Verschoor

Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
and Replication Server 15.0.1/12.5 // TeamSybase

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks & Recipes for Sybase ASE" (ASE 15 edition)
"The Complete Sybase ASE Quick Reference Guide"
"The Complete Sybase Replication Server Quick Reference Guide"

mailto:***@YOUR.SPAM.sypron.nl.NOT.FOR.ME
http://www.sypron.nl
Sypron B.V., Amersfoort, The Netherlands
Chamber of Commerce 27138666
-----------------------------------------------------------------

Post by robert
Sybase ASE 12.5.4
As per the subject, I'l looking for a way where creating a login or
changing it's password on dataserver A also happens on dataserver B,
and vice-versa.
Would it be possible to replace master..syslogins on B with a
proxy_table pointing to A? I've tried it but could not drop local
syslogins (would probably cause havoc anyway).
Any other suggestions?

[Patrick Cain]

Rob's sp_password/addlogin method sounds best, but most places I've
worked just have a job to BCP syslogins across hourly or nightly. You
can bcp it into a temporary table on the destination server then just
insert new or update changed changed passwords.

On 11 Jan, 08:19, "Rob V [ Sybase ]"

Post by Rob V [ Sybase ]
Without replication, the classic workaround is to modify the stored procs
sp_password and sp_addlogin to call the corresponding procedures in the
remote ASE servers as RPCs

[unknown]

You could inquire about LDAP logins managed externally to ASE. You still need to create the account on both servers but the
passwds would be external.
--
Cory Sane
[TeamSybase]
Certified Sybase Associate DBA for ASE 15.0

Post by robert
Sybase ASE 12.5.4
As per the subject, I'l looking for a way where creating a login or
changing it's password on dataserver A also happens on dataserver B,
and vice-versa.
Would it be possible to replace master..syslogins on B with a
proxy_table pointing to A? I've tried it but could not drop local
syslogins (would probably cause havoc anyway).
Any other suggestions?

[Jason L. Froebe [TeamSybase]]

Post by unknown
You could inquire about LDAP logins managed externally to ASE. You
still need to create the account on both servers but the passwds would
be external.

or PAM authentication :)