Date: Fri, 29 Mar 2024 06:51:47 -0400 (EDT) Message-ID: <282607021.940.1711709507890@prodopencatalystconfluence.catalyst> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_939_841193181.1711709507886" ------=_Part_939_841193181.1711709507886 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
To configure the Data Steward, you must fir= st make sure that you have created a user with Data Steward privileges. To = create a Data Steward, please follow the instructions here: SHRINE 4.0.0 Chapter 9.1 - Setting Up the Data Steward User
Find the steward section in shrine.conf . This section governs how the dat=
a steward application behaves, including its ability to send audit emails t=
o the Data Steward. Set valid email addresses in the 'From' and 'To' fields=
. Set the externalStewardBaseUrl to the URL your Data Steward should use fo=
r the data steward application. (The email contains a link to help easily s=
tart the audits.)
shrine { ... steward { createTopicsMode =3D Approved //the default is Pending - the most secur= e - but most sites use Approved emailDataSteward { //provide the email address of the shrine node system admin, to handl= e bounces and invalid addresses from =3D "shrine-admin@example.com" //provide the email address of the shrine node system admin, to handl= e bounces and invalid addresses to =3D "shrine-steward@example.com" //provide the externally-reachable URL for the data steward externalStewardBaseUrl =3D ${shrine.shrineHubBaseUrl}/shrine-api/shri= ne-steward } } // end steward ... }
If you wish to not send emails, override the sendAuditEmails =3D fa= lse in this section.
SHRINE by default assumes it can send mail via smtp on localhost port 25= . However, if your tomcat server cannot easily send email you may need to a= dd an email{} section inside of the shrine{} section in shrine.conf. SHRINE= sends emails from postfix on port 25 by default. SHRINE uses javaxmail int= ernally. Any valid javaxmail configuration values should be supported by sh= rine.conf. Here is an example that uses AWS SES:
shrine { ... email { //add javax mail properties from https://www.tutorialspoint.com/javamai= l_api/javamail_api_smtp_servers.htm here javaxmail { mail { smtp { //for postfix on localhost //host =3D localhost //port =3D 25 //for AWS SES - See http://docs.aws.amazon.com/ses/latest/Develop= erGuide/send-using-smtp-java.html =09=09 //comment out if you want to just use postfix over port 25 host =3D email-smtp.us-east-1.amazonaws.com port =3D 25 transport.protocol =3D smtps auth =3D true starttls.enable =3D true starttls.required =3D true }=20 }=20 }//end javaxmail section //Must be set for AWS SES. See http://docs.aws.amazon.com/ses/latest/De= veloperGuide/send-using-smtp-java.html authenticator { username =3D yourSESUsername } } //end email section ... }
shrine.email.java= xmail.authenticator.password =3D yourSESPassword