ad-assurance - RE: [AD-Assurance] RE: Sorry for the NTLMv1/v2 confusion
Subject: Meeting the InCommon Assurance profile criteria using Active Directory
List archive
- From: "Rank, Mark" <>
- To: "" <>
- Subject: RE: [AD-Assurance] RE: Sorry for the NTLMv1/v2 confusion
- Date: Fri, 21 Jun 2013 18:41:00 +0000
- Accept-language: en-US
- Authentication-results: sfpop-ironport04.merit.edu; dkim=neutral (message not signed) header.i=none
--------------------------------------------------
Mark Rank
Project Manager - Identity & Access Mgt UCSF Information Technology Services (ITS)
email: phn:414-331-1476
--------------------------------------------------
From: [] on behalf of Brian Arkills []
Sent: Friday, June 21, 2013 11:17 AM To: Subject: RE: [AD-Assurance] RE: Sorry for the NTLMv1/v2 confusion Sorry I missed today's call--sounds like it was real interesting. :)
A couple things:
On the Microsoft front, I saw an email today from Dean Wells, which suggests to me that he's back from leave and we could re-engage with him.
With regard to David's note, I saw a tweet yesterday about a presentation for a step-by-step on how to get rid of AD-DS and convert it entirely to the cloud based Azure Active Directory. I don't know what that presentation said about the difference in functionality, but it's on my list to read at some point. While at the TechEd presentation for the AAD graph API, there were several audience members which had questions about features for entirely cloud based enterprises. So I think there is already a small but growing contingent of folks moving away from AD-DS. But there are a lot of applications whose lowest common denominator integration for identity is Active Directory. And that's because it's so ubiquitous. We have a couple dozen of them integrating with our AD. So I don't foresee a sudden shift, but rather a slow decline with a hybrid future until you finally ditch the on-premise AD-DS.
Finally, I want to thank Ron again for previously sharing that powershell script for NTLMv1 log scraping. We're planning on putting it to good use here as we try to make a reasoned case for turning off NTLMv1.
From: [mailto:]
On Behalf Of David Walker
As long as we're waxing philosophic, I wonder how long it'll be before enterprises realize that they have diminishing reason for putting a PC on everyone's desk (and, therefore, for running AD). Enterprise services are increasingly available
on the web for BYOD mobile platforms. At some point, people will use enterprise-provided PC for not much more than legacy Windows applications (which probably won't include Exchange or maybe even Office). At that point, those legacy applications will start
looking pretty expensive. Ron:
|
- [AD-Assurance] Sorry for the NTLMv1/v2 confusion, Ron Thielen, 06/21/2013
- [AD-Assurance] RE: Sorry for the NTLMv1/v2 confusion, Rank, Mark, 06/21/2013
- Re: [AD-Assurance] RE: Sorry for the NTLMv1/v2 confusion, David Walker, 06/21/2013
- RE: [AD-Assurance] RE: Sorry for the NTLMv1/v2 confusion, Brian Arkills, 06/21/2013
- Re: [AD-Assurance] RE: Sorry for the NTLMv1/v2 confusion, David Walker, 06/21/2013
- RE: [AD-Assurance] RE: Sorry for the NTLMv1/v2 confusion, Rank, Mark, 06/21/2013
- RE: [AD-Assurance] RE: Sorry for the NTLMv1/v2 confusion, Brian Arkills, 06/21/2013
- Re: [AD-Assurance] RE: Sorry for the NTLMv1/v2 confusion, David Walker, 06/21/2013
- [AD-Assurance] RE: Sorry for the NTLMv1/v2 confusion, Eric Goodman, 06/21/2013
- [AD-Assurance] RE: Sorry for the NTLMv1/v2 confusion, Capehart,Jeffrey D, 06/21/2013
- [AD-Assurance] RE: Sorry for the NTLMv1/v2 confusion, Rank, Mark, 06/21/2013
Archive powered by MHonArc 2.6.16.