S/MIME control in Chrome

%3CLINGO-SUB%20id%3D%22lingo-sub-565019%22%20slang%3D%22en-US%22%3ES%2FMIME%20control%20in%20Chrome%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-565019%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20attempting%20to%20get%20Office%20365%20S%2FMIME%20encryption%20working%20for%20some%20of%20our%20employees%2C%20accessed%20at%20outlook.office365.com.%26nbsp%3B%20These%20employees%20have%20been%20given%20e-mail%20accounts%20with%20one%20of%20our%20customers%20as%20well%20as%20certificates.%26nbsp%3B%20They're%20able%20to%20access%20mail%20and%20use%20encryption%20through%20Outlook%2C%20but%20it%20would%20be%20a%20big%20help%20to%20get%20it%20working%20in%20webmail%2C%20preferably%20Chrome.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20far%2C%20I%20have%20used%20this%20to%20force%20install%20the%20extension%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fsecuritycompliance%2Fconfigure-s-mime-settings-for-outlook-web-app%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fsecuritycompliance%2Fconfigure-s-mime-settings-for-outlook-web-app%3C%2FA%3E%2C%20which%20worked.%26nbsp%3B%20If%20that's%20all%20I%20do%2C%20and%20we%20sign%20back%20in%20to%20the%20account%20and%20go%20to%20the%20Mail%20settings%2C%20the%20S%2FMIME%20section%20says%20we%20need%20to%20add%20outlook.office365.com%20to%20the%20allowed%20domains%20in%20the%20extension.%26nbsp%3B%20If%20we%20do%20that%20and%20restart%20Chrome%2C%20the%20S%2FMIME%20section%20disappears.%26nbsp%3B%20Remove%20the%20domain%20and%20restart%2C%20and%20it's%20back.%26nbsp%3B%20Having%26nbsp%3BSmimeOutlookWebChrome.msi%20installed%20or%20not%20does%20not%20seem%20to%20make%20a%20difference.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20I'm%20missing%20something%20simple%2C%20but%20support%20through%20the%20other%20organization%20has%20been%20difficult%20to%20get%20and%20I%20personally%20don't%20have%20an%20account%20with%20them%2C%20so%20I'm%20having%20to%20resort%20to%20digging%20something%20up%20and%20bugging%20someone%20to%20try%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-565019%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Visitor

I'm attempting to get Office 365 S/MIME encryption working for some of our employees, accessed at outlook.office365.com.  These employees have been given e-mail accounts with one of our customers as well as certificates.  They're able to access mail and use encryption through Outlook, but it would be a big help to get it working in webmail, preferably Chrome.  

 

So far, I have used this to force install the extension: https://docs.microsoft.com/en-us/office365/securitycompliance/configure-s-mime-settings-for-outlook-..., which worked.  If that's all I do, and we sign back in to the account and go to the Mail settings, the S/MIME section says we need to add outlook.office365.com to the allowed domains in the extension.  If we do that and restart Chrome, the S/MIME section disappears.  Remove the domain and restart, and it's back.  Having SmimeOutlookWebChrome.msi installed or not does not seem to make a difference.

 

I think I'm missing something simple, but support through the other organization has been difficult to get and I personally don't have an account with them, so I'm having to resort to digging something up and bugging someone to try it.

 

 

0 Replies