Skip to main content

PingFederate SSO Now Integrated into Microsoft’s Azure Active Directory Connect

 Microsoft Azure Active Directory.
Office 365 users have long used Microsoft’s Azure Active Directory Connect wizard to establish a connection between the Active Directory and Microsoft’s Azure AD in the cloud. The wizard’s interface now includes an option to use PingFederate to establish this connection. This feature was briefly seen in beta back in May of this year, but it is now released for the general public to use.
PingFederate is Ping Identity’s enterprise identity bridge which allows for single sign-on. The SSO feature allows users in enterprises to use a single set of credentials to access multiple enterprise bought services. PingFederate offers centralized identity management, access management, device identity management, API security, and social identity integration. The service facilitates SSO using SAML, WS-Federation, WS-Trust, OAuth, OpenID Connect, and SCIM.
As the use of Azure AD as a cloud-based identity management service for enterprises has been growing, Microsoft’s collaboration with Ping Identity has brought PingFederate into the connection wizard’s interface permitting enhanced single sign-on capabilities for the service. The integration allows administrators to quickly set up user identities for enterprise employed Office 365 applications and allow seamless single sign-on to these services through the PingFederation integration.
Once the Federation with PingFederate settings are configured, users are able to sign onto Microsoft’s cloud and Office 365 services and applications with the same credentials off premises as those that they use to access these services on the enterprise’s local network. PingFederate allows users to maintain the same logon irrespective of the location of access or the service that is being accessed as long as the identity for the user has been created and the identity has been given account access to the Microsoft applications through the enterprise PingFederate administrator.
To configure Federation with PingFederate, you must first ensure that PingFederate 8.4 or higher is being used and you have the SSL certificate for the federation service that you are attempting to configure access for. The first step in the configuration process is the verification of the Azure AD Domain that you intend to federate. Next, you must export the PingFederate settings and send this information to your PingFederate enterprise administrator. S/he will provide you with a server URL and port number for your access accordingly which Azure AD will then verify on your end. Once Azure AD Connect verifies the metadata you fed it back form your administrator, it will resolve endpoints from your local DNS as well as an external DNS. Now that the domain has been configured successfully, you can enter your logon credentials which will also be verified before your PingFederate configuration is complete.
A document with instructions for the use of Azure AD Connect has been published on Microsoft’s website. The documentation contains all setup, troubleshooting, and mitigation advisories for the service.

Comments

Post a Comment

Popular posts from this blog

How to Fix Windows 10 Pin Issues when Logging In

Windows 10 provide a very convenient way of logging in to your Windows using a pin code. However, some users are experiencing problems with the Windows 10 pin login. After a Windows Update, users can’t sign in using their previous pin code. And this isn’t related to users forgetting their pin codes. It seems like their old pin code has been removed from the Windows and their PCs aren’t recognising it. Now, there are a lot of scenarios of this. Some people can’t sign in because the system doesn’t recognise their PIN. On the other hand, some people can’t even enter their pin because there isn’t a pin option available for them. What Causes the Pin to Stop Working? Here is a list of things that can cause this issue A bug in the Windows Update that might have broken the PIN sign in option Corrupt files in the Ngc folder Usually it happens after a Windows Update so it’s a bug that breaks the PIN sign in option. Tips Before you dive deep in to the methods given below...
Post a Comment
Read more

How to Fix the ‘Failed to Acquire the VirtualBox COM Object’ Error

Several users are reporting that they are unable to launch VirtualBox. The critical error message that comes up is  “Failed to acquire the VirtualBox COM object. The application will terminate”.  In some cases, the error is also accompanied by a second error message pointing towards the problem. The issue does not seem to be specific to a certain Windows version since it’s confirmed to occur on both Windows 8.1 and Windows 10. Failed to acquire the VirtualBox COM object. The application will now terminate. What is causing the ‘Failed to Acquire the VirtualBox COM Object’ error? We investigated this issue by looking at various user reports and the repair strategies that are commonly deployed successfully in this particular scenario. As it turns out, there are multiple culprits that might end up triggering this issue: VirtualBox is not installed with admin access  – Virtualbox is one of those software products that will require you to install them with a...
Post a Comment
Read more

Fix: System Found Unauthorized Changes on the Firmware, Operating System or UEFI Drivers

Several users are struggling with the  System found unauthorized changes on the firmware error  at every startup or when trying to take their computer out of hibernation mode. Most affected users report that the issue started occurring after they installed some pending Windows updates. The issue is mostly encountered on Windows 7. The system found unauthorized changes on the firmware, operating system or UEFI drivers. Press [OK] to run the next boot device, or enter directly to BIOS Setup if there are no other boot devices installed. What is causing the System found unauthorized changes on the firmware error We investigated this particular issue by looking at various user reports. This error will occur whenever your system is checking the firmware one some computer hardware parts as part of a new security feature. To be precise, the error is occurring because not all Windows versions will support this new security feature. As it turns out, there are sev...
Post a Comment
Read more