# #####################################
|
# Kerberos Module (optional)
|
#
|
# jvm.java.security.krb5.kdc: This should be the IP/FQDN of the KDC server. The value will be set to JVM's
|
# java.security.krb5.kdc.
|
#
|
# jvm.java.security.krb5.realm: This is the default REALM for Kerberos. It is being used for JVM's
|
# java.security.krb5.realm.
|
#
|
# mms.kerberos.principal: The principal we used to authenticate with MongoDB. This should be the exact same user
|
# on the mongoUri above.
|
#
|
# mms.kerberos.keyTab: The absolute path to the keytab file for the principal.
|
#
|
# mms.kerberos.debug: The debug flag to output more information on Kerberos authentication process.
|
#
|
# Please note, all the parameters are required for Kerberos authentication, except mms.kerberos.debug. The mechanism
|
# will not be functioning if any of the setting value is missing.
|
#
|
# Assume your kdc server FQDN is kdc.example.com, your Kerberos default realm is: EXAMPLE.COM,
|
# the host running MMS app is mmsweb.example.com, the Kerberos for MMS is mms/mmsweb.example.com@EXAMPLE.com,
|
# And you have a keytab file for mms/mmsweb.example.com@EXAMPLE.COM located at /path/to/mms.keytab, then the
|
# configurations would be:
|
# jvm.java.security.krb5.kdc=kdc.example.com
|
# jvm.java.security.krb5.realm=EXAMPLE.COM
|
# mms.kerberos.principal=mms/mmsweb.example.com@EXAMPLE.COM
|
# mms.kerberos.keyTab=/path/to/mms.keytab
|
# mms.kerberos.debug=false
|
#
|
# ####################################
|
#jvm.java.security.krb5.kdc=
|
#jvm.java.security.krb5.realm=
|
#mms.kerberos.principal=
|
#mms.kerberos.keyTab=
|
#mms.kerberos.debug=
|