SUMMARY:

• Microsoft Identity Manager, Forefront Identity Manager 2010, AADConnect, DirSync & ILM
• Changes to: Schema (Metaverse & Portal) and RCDC
• Rule, Password and Metaverse extensions (classic)
• Declarative MPR, WF, Set
• MA’s - AD, FIMMA, SAP, Oracle, SQL, Powershell, Custom Complex ECMA
• Custom Workflows (WF) for MIM/ Confidential
• Custom web services code to Confidential web service engine
• User and Group Management
• SSPR (Self Service Password Reset), BHOLD, Role Based Access Control (RBAC)
• MIM WAL and Confidential Proxy
• AD password filters (C++)
• Privileged Access Management (PAM)
• Azure AD, AADConnect & DirSync
• Identity and Access Azure AD, Azure B2C, Azure B2B, Azure MFA, AAD Connect, Azure Key Vault for TDE and secrets, Azure RBAC
• Sql Server, Oracle, Sybase, Access, SSRS, SSIS, DTS, Analysis Server
• C#, VB.NET, ASP.NET 1,0(alpha)-5.x, Core, C++, Powershell, CLI
• OOP, OOD, UML, Active Directory, SunOne, Open, iPLanet
• Modern Protocols (OAuth, Open ID Connect SAML), Legacy Protocols (Kerberos, NTLM)
• Web Services, MSMQ, Windows Services
• Modern Protocols (OAuth, Open ID Connect SAML)
• ADFS, O365, LIVE
• SAP ABAP & SAP ERP Simulation BI class
• Inventor of many patents in software industry such as the Confidential ®.system .
• Have spoken at various .NET activities such as El Paso Code Camp on topics such as Building Server Side Controls.
• DotNetNuke originating contributors helping lead to its success. Adopted my code base that became version 2.0.
• Certifications: MCTS Forefront Identity Manger ( Confidential ) 2010, MCITP Sql Server, MCAD.NET C#, CompTIA Security+
• Trained in Okta IDM trained, SAP ABAP

PROFESSIONAL EXPERIENCE:

Confidential

Identity Consultant - MIM

Responsibilities:

• Identity and Access Architecture for NATO Modernization
• Microsoft Identity Manager (MIM)
• Pending TS clearance
• Privileged Access Management (PAM)

Confidential

Senior Consultant - MIM

Responsibilities:

• Custom redesign of existing MIM ECMA connector’s internal Web Services and DB’s managing users. Approximately 700k External Users and 5k Internal Users.
• O365 Licensing and deployment
• Migration from DirSync to AADConnect
• Azure Key Vault Implementation to Sql Databases.
• IDAM database that acts as interface to MIM. Used as a provisioning as communication tool to via web service to databases, Data Warehouse, along with API for
• Design of RBAC implementation
• Reviewed and made formal recommendations on existing M/ Confidential Implementations that I am in process of implementing such as (more detail can be provided)
• Best practices not being followed
• Performance problems - various
• Improper error handling
• Direct to Confidential Sync
• Documentation
• Duplicate Connector Space objs
• Sql problems
• Indexing
• Alias missing
• Patching
• DR and Recovery methods
• Designed Sql Server cluster for MIM environment.
• Designed the enhanced Sql Server Database Security Standards
• Deployment off existing cluster to new cluster
• Complex solution involving same object type with multiple connector space objects to join to same metaverse. Normally this would cause an ambiguous error, but done to provide a correlation Id back to the objects.
• Migration from DirSync to Azure AD Connect (AADConnect)
• Azure Key Vault Implementation for Secrets, Keys, and TDE encryption throughout the organization.

Confidential

Senior Consultant -MIM

Responsibilities:

• Custom complex Confidential ECMA connectors to third party Web Services managing users and groups for large automobile manufacturer. Solved many problems with a Web Service that was lacking in flexibility related to Confidential . Rule and Metaverse extensions
• Designed and deployed SSPR for external users of a State Governments interface to their systems. Custom web services for user and group provisioning to Confidential 2010 R2.
• Reviewed and made recommendations on multiple Confidential Implementations
• Currently in Rewrite and Rebuild current environment
• Maintain daily Confidential tasks.
• Design and Deployment
• Architecture
• Custom WCF Web Services to Confidential service to provision groups and users immediately in AD and Confidential
• Confidential User and Group provisioning
• SSPR
• Custom Workflows
• Confidential Proxy, Confidential WAL
• BHOLD Web Services
• Reviewed and made recommendations on several Confidential Implementations - Large Canada Bank, Large County Government and State Department of Health.
• Rule, Password, Metaverse extensions
• Inspection of Confidential Implementation correcting many errors in systems

Confidential

Senior Consultant - MIM Owner

Responsibilities:

• Design and Configure Confidential 2010 port objects
• Design and Configure Synchronization Engine for Identity Synchronization with AD, LDAP, Lotus Notes and SQL DB targets.
• Document Design, Testing and Implementation processes.
• Custom Confidential Workflows using VB/C#.NET for process automations.
• Create/Configure SQL Procedures/Triggers for Confidential Integrations. Sql CLR to AD.
• Custom SSRS to AD/ Confidential side by side.
• EnSync’s Medco Confidential GalSync Test lab for data merge from Medco and Express Scripts
• Department of Education, State of Arizona. Confidential implementation envisioning phase. Planned implementation.
• New Mexico State University move to Cloud of 65,000 student and faculty identity information using MS Confidential 2010 from Banner, Active Directory, SunOne, and Microsoft Live.
• Systems used were Banner, Active Directory, SunOne, and Microsoft Live.
• Set up all Password Synchronization from AD to other systems using PCNS.
• Oracle MA Password Synchronization
• Provisioned Users in Outlook Live and Sun LDAP. Wrote MA for Sun Extension to provision attributes and groups in Sun.
• Provisioned Groups from Outlook Live to AD by writing a MA that pulled Groups from Outlook Live down to AD. This is wrapped around the OLSYNC dll further complicating the agents.
• Attributes flowed from various systems (Banner, AD, Sun, and Outlook Live). See the unfinished documentation on attribute Flow ( uid:protect pwd:testtest)
• Initially, Wrapped OLSYNC MA to allow multiple MetaVerse dlls to provision data to the MV. Configuration wrapped all the OLSYNC built in MA around the provisioning, exportation of attributes to Sun, Oracle, Live, and AD. This was done initially at the recommendation of MS. However, later on we discovered because of various OLSYNC issues, the ideal solution was to have 2 Confidential solutions. 1) With strictly OLSYNC and the agents that are associated with it 2) Agents where data flowed normally out of AD/Banner to Sun Open Ldap.
• Custom SSIS jobs to update Active Directory attributes from CSV’s that flowed through Confidential to other systems.
• Wrote custom Active Directory Password Filter (C++) to validate a password across all the existing systems (Outlook Live, AD, Sun, and Oracle), to meet the needs of all the passwords of all these systems.
• Gathered business rules from Stakeholders to enable the University to have a Confidential solution.
• Moved all of the email and wrote all the Confidential MA’s, custom code, password sync, move of student data to Microsoft Live.
• Discovered Flaw in Microsoft email migration utility. Wrote a process of writing solution to find missing email across 7 TB of data. MS is in joint collaboration on process with MS.