Page History

UNDER CONSTRUCTION

1. email.address.from:

1. • Description

1. • :  A string containing an email address from whom the email is being sent.  The string may contain more than just an email address.
   • Usage:  Optional
   • Example:  email.address.from=registration@mit.edu

1. • ("MIT

1. • Office

1. • of

1. • the

1. • Registrar")

1. • Dependencies

1. • :  If specified,

1. • this

1. • value

1. • will

1. • always

1. • be

1. • used

1. • in

1. • the

1. • from

1. • field

1. • of

1. • the

1. • email.

1. • If not specified, the CSF Email Service default address (csf-support@mit.edu) will be used.
2. email.address.test.to:

1. • Description

1. • :  A string containing an email address to whom the email is being sent.
   • Usage:  Optional.  Recommend to be used on WORKSTATION, DEV, TEST and QA servers and not used on PRODUCTION servers.
   • Example:  email.address.test.to=rjrenolds@mit.edu

1. • Dependencies

1. • :  Used in conjunction with the email.production.mode

1. • property.

1. • 
       When

1. • email.production.mode=false:

1. • 
         email will be sent to the email address specified with this property.
       When

1. • email.production.mode=true:

1. • 
         email will be sent to the email address specified by the calling application.
     If no "to address" is determined in either of the above cases, the CSF Email Service default address (csf-support@mit.edu) will be used.
2. email

1. .address.bcc:

1. • Description

1. • :  A string of CSV email address(es)

1. • to

1. • be

1. • used

1. • in

1. • the

1. • email's

1. • bcc.

1. • Usage

1. • :  Optional
   • Example:  email.address.bcc=rjrenolds@mit.edu

1. • Dependencies

1. • :  Used in conjunction with the email.production.mode

1. • property.

1. • 
       When

1. • email.production.mode=false:

1. • 
         bcc addresses will not be added to the emails.
       When

1. • email.production.mode=true:

1. • 
         bcc addresses will be added to the emails.
2. email.production.mode:

1. • Description

1. • :  Used to indicate whether or not the applicaition is deployed on a production server.
   • Usage:  Optional. Only the boolean values true or false are allowed (default is false).
   • Example: 
       When

1. • email.production.mode=false:

1. • 
         the application is deployed to DEV, TEST or QA server and is not deployed to a PRODUCTION server.
       When

1. • email.production.mode=true

1. • :
         the application is deployed to a PRODUCTION server.
   • Dependencies:  None.
2. email.app.id:
   • Description: Used to identify the application that created the email.
   • Usage: Required.
   • Example: email.app.id=ssb
       In this example, the application id is ssb and must be unique.
   • Dependencies: The application id must be unique. In other words, each application must have its own unique email.app.id value.
3. email.sendEmailSchedule:
   • Description: Used to set the time interval for sending emails. The property value follows the format for the Quartz cron trigger. IMPORTANT: in a clustered environment (i.e. TEST and PROD), this property should be different for every server in the cluster: we want to avoid multiple quartz jobs running against the same email data at the same time and sending duplicate emails. In fact we recommend effectively disabling the quartz job on all but one of the servers in a given cluster by specifying a schedule that will never be triggered (e.g. a data in the year 2099).
   • Usage: Required when using csf-email in a cluster. If not specified, the csf-email default schedule will be used (every 10 minutes starting at the top of the hour).
   • Example: email.sendEmailSchedule=0 0/20 0-22 * * ?
       In this example, the emails will be send every 20 minutes, at 0, 20, and 40 minutes past the hour.
   • Dependencies: none.
   • Recommended Settings In Clustered Environment (TEST/PROD):
     one server in cluster (e.g. sea-app-5 in TEST): email.sendEmailSchedule=0 0/10 0-22 * * ?
     other server(s) in cluster (e.g. sea-app-6 in TEST): email.sendEmailSchedule=0 * * * * ? 2099
4. email.deleteEmailSchedule:
   • Description: Used to set the time interval for deleting emails that have been sent. The property value follows the format for the Quartz cron trigger. IMPORTANT: in a clustered environment (i.e. TEST and PROD), this property should be different for every server in the cluster: we want to avoid multiple quartz jobs running against the same email data at the same time. In fact we recommend effectively disabling the quartz job on all but one of the servers in a given cluster by specifying a schedule that will never be triggered (e.g. a data in the year 2099).
   • Usage: Required when using csf-email in a cluster. If not specified, the csf-email default schedule will be used (nightly at 10.30pm).
   • Example: email.deleteEmailSchedule=0 45 23 * * ?
       In this example, the emails will be deleted every night at 11.45pm.
   • Dependencies: none.
   • Recommended Settings In Clustered Environment (TEST/PROD):
     one server in cluster (e.g. sea-app-5 in TEST): email.deleteEmailSchedule=0 30 22 * * ?
     other server(s) in cluster (e.g. sea-app-6 in TEST): email.deleteEmailSchedule=0 * * * * ? 2099

email will be sent to the email address specified with this property.

email will be sent to the email address specified by the calling application.

bcc addresses will *not* be added to the emails.

the application is deployed to DEV, TEST or QA server and is *not* deployed to a PRODUCTION server.

the application is deployed to a PRODUCTION server.

1. local.mitroles:

1. • Description

1. • :  A csv string of application defined roles.
   • Usage:  Optional.  Only to be used on developer workstations.  Do not use on servers.
   • Example:  local.mitroles=SSB_ADMIN,SSB_PAYMENT,SSB_REPORTS.

1. • Dependencies

1. • :

1. • 
       Will only be used if local.authentication=true

1. • and

1. • local.mitroles

1. • contains

1. • a

1. • non-empty

1. • string.

1. •   Otherwise, the uaws or rolesws webservice will be used to get the user roles.
2. local.mitroles.domain:

1. • Description

1. • :  A string containing the application defined ROLES DB 3 character catagory.
   • Usage:  Optional.  Only to be used on developer workstations.  Do not use on servers.
   • Example:  local.mitroles.domain=SFS.

1. • Dependencies

1. • :  Will only be used if local.authentication=true

1. • and

1. • local.mitroles

1. • contains

1. • a

1. • non-empty

1. • string.

2. local.mitroles.function:

1. • Description

1. • :  A string containing the application defined ROLES DB 3 character function.
   • Usage:  Optional.  Only to be used on developer workstations.  Do not use on servers.
   • Example:  local.mitroles.function=SSB.

1. • Dependencies

1. • :  Will only be used if local.authentication=true

1. • and

1. • local.mitroles

1. • contains

1. • a

1. • non-empty

1. • string.

2. local.authentication:

1. • Description

1. • :  A boolean value indicating whether or not TOUCHSTONE authentication is to be used.
   • Usage:  Required.
   • Example:  Only the boolean values true or false are allowed.
       When

1. • local.authentication=false:

1. • 
         Touchstone will be used to authenticate the user.  Always set this value to false when deployed to a server.
       When

1. • local.authentication=true:

1. • 
         Authentication will be done via a local dialog box.  User will be prompted to enter the local.user.name

1. • and

1. • local.user.password.

1. • Dependencies

1. • :  None.
2. local.user.name:

1. • Description

1. • :  A sting containing an abitrary user name.
   • Usage:  Optional.  Only to be used on developer workstations.
   • Example:  local.user.name=jblow.

1. • Dependencies

1. • :  Will only be used if local.authentication=true.

2. local.user.password:

1. • Description

1. • :  A sting containing an abitrary user password.
   • Usage:  Optional.  Only to be used on developer workstations.
   • Example:  local.user.password=mypassword.

1. • Dependencies

1. • :  Will only be used if local.authentication=true.

Touchstone will be used to authenticate the user.  Always set this value to *false* when deployed to a server.

1. .proxy.user:
   • Description:  A string containing the ROLES DB proxy user that is used by the CSF authorization service.  This is assigned by the ROLES DB administrator.  Current values are: REG$PRD, REG$TST, SFS$PRD, SFS$TST, GRAD$PRD, GRAD$TST.  Verify with your team leader as to which proxy user you should use.
   • Example:  roles.proxy.user=SFS$TST.
   • Usage:  Required.
   • Dependencies:  None
2. roles.function.category:
   • Description:  A string containing the application defined ROLES DB 3 or 4 character catagory.  The 3 or 4 character catagory is assigned by the ROLES DB administrator.  The current valid categories are REG, SFS and GRAD.  Once you have selected the category, you must use it's corresponding proxy user.
   • Usage:  Required.
   • Example:  roles.function.category=SFS.

1. • Dependencies

1. • :

1. • 
       Will only be used if local.authentication=false

1. • or

1. • local.mitroles

1. • has

1. • not

1. • been

1. • used.

1. •   This will override the default
       category (REG)

1. • used

1. • by

1. • the

1. • uaws

1. • webservice

1. • when

1. • retrieving

1. • the

1. • user's

1. • roles

1. • from

1. • the

1. • ROLES

1. • DB.

2. roles.function.function:

1. • Description

1. • :  A string containing the application defined ROLES DB 3 character function.  The 3 character function is assigned by the ROLES DB administrator.
   • Usage:  Optional.
   • Example:  local.mitroles.function=SSB.

1. • Dependencies

1. • :  If specified,

1. • this

1. • property

1. • will

1. • only

1. • be

1. • used

1. • if

1. • local.authentication=false

1. • or

1. • local.mitroles

1. • is

1. • not

1. • used.

2. webservices.mitrolesws.proxy.user:

1. • Description

1. • :  A ROLES DB proxy user that will be used by the uaws webservice when retreiving the user's authorizations.  The ROLES proxy user is assigned by the ROLES DB administrator.
   • Usage:  Required.  Used only with the WebServiceRoleswsSao listAuthorizationsByCriteria method.
   • Example:  webservices.mitrolesws.proxy.user=REG$PRD.

1. • Dependencies

1. • :  None
2. webservices.mitroles.url:

1. • Description

1. • :  The URL to the uaws webservice.
   • Usage:  Required.
   • Example:  webservices.mitroles.url=https://mv-ezproxy-com.ezproxyberklee.flo.org/uaws/services/ua.

1. • Dependencies:  None
2. webservices.mitrolesws.url:
   • Description:  The URL to the rolesws webservice.
   • Usage:  Required.
   • Example:  webservices.mitrolesws.url=https://mv-ezproxy-com.ezproxyberklee.flo.org/rolesws/services/roles.
   • Dependencies:  None

2. webservices.keyStore:

1. • Description

1. • :  The Java keystore that is used to authenticate to the uaws webservice.
   • Usage:  Required.
   • Example:  webservices.keyStore=/certificates/keystores/registrar.jks.

1. • Dependencies

1. • :  None
2. webservices.keyStorePassword:

1. • Description

1. • :  The password for the Java keystore.  You can get the password from ops.
   • Usage:  Required.
   • Example:  webservices.keyStorePassword=changeit.

1. • Dependencies

1. • :  None
2. webservices.trustStore:

1. • Description

1. • :  The server trust store that is used to authenticate to the uaws webserver.  You can download the serverTrustStore.jks now.
   • Usage:  Required.
   • Example:  webservices.trustStore=/certificates/keystores/serverTrustStore.jks.

1. • Dependencies

1. • :  None
2. webservices.trustStorePassword:

1. • Description

1. • :  The password for the Java truststore.
   • Usage:  Required.
   • Example:  webservices.keyStorePassword=changeit.

1. • Dependencies

1. • :  None