PingIdentity Articles

Here are some important links for PingFederate for reference. In December 2017, new versions for PingFederate 9 and PingAccess 5 were released. Read here the vendor availability release.


Default Login for PingFederate Administrator console https://PingFederate_hostname:9999/pingfederate/app is the default URL  (login with username as Administrator and password)

Default Login for PingAccess Admin console https://PingAccess_hostname:9000/login is the default login URL   (login with username as Administrator and password)

PingFederate 9 documentation
 What's new in PingFederate 8.4
What's new in PingAccess 4.3
IdP-initiated SSO—POST  (link check Dec20)
SP-initiated SSO—POST-POST 
SP-initiated SSO—Redirect-POST

 Single sign-on with PingFederate
How to configure IE, chrome browser for Kerberos and NTML
PingFederate Release Notes 
Industry Standards
SAML 2.0 profiles  (SSO profile variations offered by PingFederate)
Integrate PingID with your VPN 
Kerberos Adapter 
HTML Form Adapter 
What is Token Mediation
Token Mediator Site Authenticator 
Configure ADFS as Claims Provider with PingFederate using WS-Federation
Configure SalesForce as Service Provider and ADFS as Identity Provider (applies similarly for PingFederate)

 Monitor PingFederate server via Heartbeat URL: PingFederate provides an out of the box https url which can provide the status of the PingFederate server. Typically this url (https://PFservername/heartbat.ping) can be periodically polled by a Load Balancer. Say if your PingFederate cluster consists of 4 nodes then configure the Load Balancer to check the heartbeat url for each of the individual PingFederate nodes. However if the Load Balancer is configured to poll every 5 seconds then it can increase the size of the server logs. Refer this to reduce/adjust the server logs so as not include or log the heartbeat messages.
One may supplement monitoring with third party monitoring tools such as SolarWinds. SolarWinds can monitor the heartbeat URL, server CPU of the PingFederate servers and poll via ICMP ping as well.

Enabling PingFederate version 7.x Hearbeat URL

Note about Hearbeat
Always access the Hearbeat via a HTTP GET request (not a Head request). The /pf/heartbeat.ping endpoint will only return an HTTP 200 code and "OK" as the body of the response if an HTTP GET request is made to that endpoint. The monitor or load balancer that is sending a HEAD request to this endpoint should be reconfigured to use the GET verb. (else it will return a 500 error).

PingFederate Runtime properties file (this file can be customized for runtime and Administrative console behavior)

PingAccess Heartbeat monitoring

How to configure SNMP with PingFederate (version 8.x, 9.x)
PingFederate server provides support with SNMP protocol. Using a SNMP Management console can provide info about PingFederate operational status, such as uptime since server start-up.
The MIB file for SNMP support is already available in PingFederate instalation, under the PF_Install_ Directory/pingfederate/SNMP directory
Configure access to SNMP monitoring on the PingFederate under the Server Configuration > Server Settings > Runtime Reporting screen.

Configure Gets and Traps (both are optional)
Optional: Enable Gets
  1. Select the Respond to Get Requests check box.
  2. Modify the Local Agent Port and the Community Name field values as needed.
Optional: Enable Traps
  1. Select the Generate Traps check box.
  2. Provide the required information for your network-management console and modify the "Heartbeat" Interval field value as needed.
  3. Click Test SNMP Configuration to send a single Trap to your network-management console and verify the result.


Comments

Post a Comment

Popular posts from this blog

VMware fix for Invalid manifest and ova file import failed errors

Image
Recently we got a OVA file for a virtual machine. The vendor instructions were to import the ova file in vmware Workstation, Player for Windows/Linux, Fusion for Mac, and VirtualBox as well.  The instructions were to take the available package and launch the VM with VMware workstation. The package contained  Module.mf, Module.ovf and Module-disk.vmdk and a Module.ova file. The .mf and .ovf file were 2 KB each whereas the vmdk was several gigs. The package also contained a Module.ova file which was several gigs as well. OVF           Open Virtualization Format MF             Manifest file VMDK       Virtual Machine Disk OVA           Open Virtualization Appliance The ovf file is a xml file that contains metadata for the ovf package The mf file contains the SHA1 hash codes of all files in the package The vmdk file is the disk image of the virtual machine,  VMware Workstation or VirtualBox. (vmdk format was originally developed by VMware and is an open format now). All of
Read more

SOAPUI - import certificate

Image
Note: SoapUI has two versions, one is open source and second Professional version. The open source can be download here . (confirmed link 12/19/2018). SSL Handshake issue:   There is an Issue in SoapUI version 5.3.0 (and 5.2.0 version) with SSL handshake error. It was resolved by updating below in vmoptions file ( refer here ). However, the error that shows up while trying to load wsdl is "Error loading WSDL" as below The fix is to Enable TLS 1.2 protocol for SOAP/REST calls in SoapUI, by ammending the vmoptions file to add the directive for TLS as (-Dsoapui.https.protocols=TLSv1.2). Refer here . Update: Version 5.5.0 does not have this issue. If you are on 5.3.0 better upgrade to 5.5.0 which is available now (Feb 2019). I had above issue as well as another issue reaching to https endpoint. Upgrade to 5.5.0 resolved issue. Select "Check for updates" under the Help menu and you will get option for upgrade. Select upgrade current version and accept all defaul
Read more

Session Timeout in Oracle Access Manager

Image
Session Timeout in Oracle Access Manager (OAM) The session lifetime and Idle timeout entries control how long a user's session is valid. In OAM, a user session is an object which represents an authenticated user. This object is stored in the server memory and if Database session persistence is enabled, this object is stored or available in the database. Each session is unique and is identified by both a userid and Session ID (session identifier), see screenshot below "OAM User Session Management".  A valid session means a user has been authenticated with OAM. A session can have following three states: 1) active 2) inactive 3) expired When a session is created it is in active state and is available as an object in the OAM. After a set time - idle timeout, the session moves or transitions to inactive state. And finally after the Session Lifetime time, the session is marked as expired. Expired sessions are removed from server memory. Read more about Session Lifetime
Read more