3 ms·
Interestingly, the GSA which supplied that data to the NY Times has also moved to Google Apps in 2011: http://googleenterprise.blogspot.com/2011/07/gsa-has-gone
by josefresco 14y ago
Interestingly, the GSA which supplied that data to the NY Times has also moved to Google Apps in 2011: http://googleenterprise.blogspot.com/2011/07/gsa-has-gone-google.html http://googleenterprise.blogspot.com/2011/07/gsa-has-gone-go...
- chayesfss 14y agoI know, we provide their SSO & 2fa solution for access (mail.google.com/a/gsa.gov is a public website as is secureauth.gsa.gov) along with many other government agencies. I've done many identity provider installs, google apps always goes great, office 365, not so much. MS requires them to have adfs which is basically a horrible offering (want to get rid of exchange, here, install all of these adfs servers on premise). Don't get me started.
- clauretano 14y agoIsn't it fun to explain that to provide SSO to Office 365 you effectively need 8+ ADFS servers and a couple of pairs of load balancers (or NLB) spread across at least two data center locations?[1] At least now dirsync is 64-bit so they've removed the "don't run this on your ADFS server" bit. [1]https://devcentral.f5.com/blogs/us/big-ip-and-adfs-part-1-ndash-ldquoload-balancing-the-adfs-farm-rdquo https://devcentral.f5.com/blogs/us/big-ip-and-adfs-part-1-nd...
- chayesfss 14y agoand there's the little part about adfs not including any integrated two-factor for external users. Someone can basically sit here all day and bang away at mail.google.com/a/doi.gov with accounts like Bob_Abbey@ios.doi.gov or Ken_Salazar@ios.doi.gov (just google @ios.doi.gov) and it'll never lock out access from your ip.