![]() You may also work with VMware support to extend the expiration date for ALL basic accounts from the default 30 days to 9999 days. After the setup procedure, SEG uses Certificate/CMS for authentication and, therefore, basic credentials are only required to establish initial communication.” “In environments in which basic authentication was used during the initial installation of the SEG (V2 or Classic) updated credentials will only need to be used when upgrading or reinstalling the SEG. Per the link below, however, this would be OK until you are ready to upgrade your SEG at which point a new credential might need to be set.ĪPI calls blocked if Basic Admin account authentication is past the password expiration period Like any basic account, the credential expires after 30 days starting with console version 9.4 which applies to the SEG Admin account as well. ![]() It does not need access to the console other than making an API call. In here, you must grant Edit permission (confirmed with VMware support.)Ĭreate an SEG Admin Account. I suggest creating both the “SOAP API General” role and the SEG Admin Account required during SEG configuration now before proceeding further. ![]() You may also enable REST API ahead of SEG V2 migration. hardware, software, network, certificate, etc.) within the link. Pre-requisites for Implementation of SEG (Classic Platform)įollow the relevant sections (i.e. Configure the Classic Platform with the SEG Setup Wizard.Configure the Classic Platform – Moved down from step 2.Enable Basic Authentication – Moved up from step 3.Pre-requisites for Implementation of SEG (Classic Platform).I also confirmed with VMware support on this. ![]() My sequence with this setup is a little different from what AirWatch recommends per their online documentation. My screenshots were based on console version 9.4 and SEG version 9.5. The same goes for either console version 9.x or 18.xx and above. Steps should be relatively the same whether it be Exchange 2010, 2013 or 2016. While support for Secure Email Gateway (SEG) Classic is going away by early May 2019, it’s still worth documenting for those who may not be ready to set up or migrate to SEG V2 just yet. This post was modified on 04/26/19 to include clarification on the credential expiration issue with the local SEGadmin account. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |