Globus Connect Server configuration (Stanford-specific), part 2 for legacy MyProxy authentication

globus-connect-server.conf

; vim: filetype=dosini : nospell :

;------------------------------
; Globus Configuration, Part 2
; Legacy MyProxy Authentication
;------------------------------

; This is the part of /etc/globus-connect-server.conf that is specific to the
; legacy MyProxy authentication method.  You should add this content to the
; end of the file, after you have filled in the content for Part 1.

; Part 1 is available here:
; https://gist.github.com/akkornel/b609c892271fa11fcf0504e07d6ed3f3

; Instructions related to this part are available here:
; https://globus.stanford.edu/server/myproxy.html

; NOTE: If you change anything in this file, you must re-run the
; globus-connect-server-setup command.

; This section tells globus-connect-server-setup that you are
; going to use legacy MyProxy authentication.  There is
; nothing to customize in this section.
[Security]
FetchCredentialFromRelay = True
IdentityMethod = MyProxy

; This section is where MyProxy is configured.
[MyProxy]

; This is the hostname to use for Globus to connect to your MyProxy server.
; The port number is 7512.  Globus connects to this to validate credentials.
; If you are behind a NAT, or your system's hostname does not match what is
; in public DNS, then you will need to configure this manually.
Server = %(HOSTNAME)s

; The globus-connect-server-setup program compares the system hostname to what
; you configured in the Server line, above.  If the two do not match, then
; GridFTP will be disabled.  But in NAT environments (like EC2), the mismatch
; is normal.  Setting ServerBehindNAT to True will skip the hostname check.
;;ServerBehindNAT = True