RSA Prime External: How can you support multiple SMTP From addresses

[TysonWehr]

Hi,

I have RSA SecurID Auth Manager with an AMIS (Prime External) implementation to provide an API layer on Auth Manager. We are using this to SMS and Email OTP verification to our customers.

Our business use case has broaded and now we have a new requirement requiring the business to have different "From" addresses for the Email's being sent out.

Can this be done from the workflow or email.properties or even passed in as part of the API service request?

I have tried using the workflow config, but adding new type and transport type in the workflow config is unsuccessful and all types refer back to the defeail "email" type option.

Thanks

Tyson

Note: I have tried updating the config in the verification node to add a new type "testemail" and create a corresponding transport type but it always defailts back to the basic "email" option.

<verify type="testemail" timeToLive="15">
<processor class="com.emc.rsa.pso.amis.workflow.common.verification.impl.EMAILVerificationTypeProcessorFactory" />
</verify>

And this corresponds to a transport type in 

<transport type="testemail" template="testemail.html">
<factory class="com.emc.rsa.pso.amis.workflow.common.notification.SMTPTransportProviderFactory">
<parameter name="mail.host" value="${smtp.server}"/>
<parameter name="mail.transport.protocol" value="smtp"/>
<parameter name="mail.from" value="xxxx@sxxxxx"/>
<parameter name="mail.debug" value="true"/>
<!-- <parameter name="header.X-Voltage" value="encrypt" /> -->
<!-- <parameter name="header.X-Priority" value="1" /> -->
</factory>
</transport>

[SeanDoyle · Accepted solution]

To support this functionality an enhancement is required to the SecurID Access Prime workflow service. Currently the from address is globally configured. The plan is to add the capability to override the global default at the template level or by added support for the from address to be supplied in workflow/notify calls.