Re: [HTCondor-users] Password Authentication with Python Bindings

["Fischer, Max (SCC)" <max.fischer@xxxxxxx>]

Hello Heath,

are you sure PASSWORD authentication is what you want?
The password authentication [1] is used only for daemon-to-daemon authentication. Any non-pool process, including user clients, is not supposed to use it.
A password is considered insecure if anyone but the condor pool can read it, and maps to a generic condor_pool identity.

Unless you are trying to implement your own daemon, PASSWORD authentication is very, very likely not what you want.

Cheers,
Max

[1]
http://research.cs.wisc.edu/htcondor/manual/current/3_8Security.html#SECTION00483400000000000000

> Am 20.09.2017 um 04:03 schrieb hskarlupka <heath.skarlupka@xxxxxxxxxxxxxxxx>:
> 
> Hello,
> 
> 
> I'm trying to connect to a remote scheduler with the HTCondor python bindings.  The remote scheduler is using password authentication.  I see that there is a SecMan object that can be created and a function that sets the pool password.  Its unclear to me then how the SecMan object is used by the Schedd object as there is no way to pass it into the initialization of the Schedd object.  Is there a way to  access a remote scheduler via the python bindings using a pool password?  Thank you for the help!
> 
> 
> Heath
> 
> _______________________________________________
> HTCondor-users mailing list
> To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
> 
> The archives can be found at:
> https://lists.cs.wisc.edu/archive/htcondor-users/

Attachment: smime.p7s
Description: S/MIME cryptographic signature