Technical preview version of VMware vRealize Orchestrator Plug-In for Mail

Technical preview version of VMware vRealize Orchestrator Plug-In for Mail

Technical preview version of VMware vRealize Orchestrator Plug-In for Mail

This is a patch release of the plug-in.


Version 7.0.0-3426007


  • Fix "Configure mail" standard workflow - swapped fromName and fromAddress parameters in the scripting ConnectionManager.save() call



Attachments
Comments

Hi.  I can't seem to configure the default SMTP settings to NOT use authentication.  It marks the usename and password fields as mandatory.  Further. the ConnectionManager.save() method also requires those two parameters (It will not accept null or blank as an entry), so I can't even script my way around this.  Why was this removed from the plugin?  It works without issue on my 6.0.3 vRO server.  Any suggestions for configuring the default SMTP settings for an SMTP server that does not require authentication?

Its not possible to configure the default settings in Mail plugin in 7.0.0 to use anonymous-authentication.

Another thing that is not possible is to "reset" the default config, if it is first set. I would like to be able to reset the config, if I set some values wrong.

But the ConnectionManager.save() method does not allow empty or null values.

The anonymous-authentication is possible to do, you just have to override the default setting during the "message" construction.

You just do something like this:

var message = new EmailMessage();

message.username = "";

message.password = "";

Here it is allow to use empty values, and it works.

That way you override whatever settings is in the default config, for these to settings. But you will still use the other default settings.

If you want to save default settings using ConnectionManager.save(), you just have to provide bogus information for username and password.

Another way to "achieve" a default configuration would be to store it as either a Resource Element or Configuration Element, link it to Attributes in the workflows where you want to use it.

Thanks, that did it for me.

Version history
Revision #:
1 of 1
Last update:
‎01-11-2016 12:42 AM
Updated by: