Where in the administrative console should an administrator make user attributes available as HTTP request headers?
PingAccess uses Identity Mappings to take identity attributes provided by the authentication source (e.g., PingFederate, OpenID Connect) and map them into HTTP request headers for back-end applications.
Exact Extract:
''An identity mapping allows you to map identity attributes from the user's session to HTTP headers, cookies, or query parameters that are then forwarded to the target application.''
Option A (Site Authenticators) is incorrect because Site Authenticators configure how PingAccess communicates with applications requiring authentication, not how attributes are inserted into headers.
Option B (Identity Mappings) is correct --- this is the feature designed specifically to expose user attributes to applications via HTTP headers.
Option C (Web Sessions) manages how sessions are stored and validated, but not the mapping of attributes into requests.
Option D (HTTP Requests) refers to request/response processing rules, but attributes are not mapped here.
A company uses an internally based legacy PKI solution that does not adhere to the Certification Path Validation section of RFC-5280. Which configuration option needs to be enabled when creating Trusted Certificate Groups in PingAccess?
Legacy PKIs often provide certificate chains that are out of order or non-compliant with RFC-5280 path validation. PingAccess provides an option in Trusted Certificate Groups called Validate disordered certificate chains to allow chaining even if the order is not RFC-5280 compliant.
Exact Extract:
''Enable Validate disordered certificate chains when the certificate chain is not in RFC-5280 compliant order but should still be accepted.''
Option A is incorrect; using the Java trust store is unrelated to PKI ordering.
Option B is correct --- this setting allows PingAccess to process disordered certificate chains.
Option C is incorrect; date checks are unrelated to RFC-5280 path ordering.
Option D is incorrect; revocation status handling does not address legacy PKI ordering issues.
How many administrators are supported using HTTP Basic Authentication in the Administrative Console?
When using HTTP Basic Authentication (admin.auth=native), PingAccess only supports a single administrative account (the default admin user). For multiple administrators, SSO integration (e.g., OIDC) is required.
Exact Extract:
''When admin authentication is set to native (HTTP Basic), only one administrative user is supported. For multiple admins, configure UI authentication with an OIDC provider.''
Option A (1000) is incorrect.
Option B (1) is correct --- only one basic auth admin account.
Option C (10) and Option D (100) are incorrect.
An application requires MFA for URLs that are considered high risk. Which action should the administrator take to meet this requirement?
PingAccess allows fine-grained authentication enforcement by applying Authentication Requirement rules at the resource level. These rules can invoke MFA flows based on request context or policy.
Exact Extract:
''Authentication requirement rules determine whether PingAccess challenges a user to authenticate again (for example, with MFA) before allowing access to a protected resource.''
Option A is incomplete. Creating a requirement does nothing unless it is applied.
Option B is correct because applying the Authentication Requirement rule to the specific resource (URL) enforces MFA only for that resource.
Option C is incorrect; Web Session Attribute rules are about evaluating existing session attributes, not triggering MFA.
Option D is incorrect; HTTP Request Parameter rules are used to evaluate request data, not enforce MFA policies.
A business application must be accessible via two FQDNs. Which PingAccess functionality should an administrator use to meet this requirement?
Virtual Hosts in PingAccess define the external FQDNs (and ports) through which applications are accessed. An application can be bound to multiple virtual hosts to allow access via multiple FQDNs.
Exact Extract:
''A virtual host specifies the fully qualified domain name and port number through which an application is accessed.''
Option A (Virtual Hosts) is correct --- multiple FQDNs can be supported by assigning multiple virtual hosts.
Option B (Applications) define resource protection but do not manage FQDN binding.
Option C (Sites) define back-end targets, not the public-facing FQDN.
Option D (Web Sessions) handle authentication state, unrelated to hostnames.
Shenika
9 days agoFiliberto
16 days agoIzetta
24 days agoBarrett
1 month agoJaime
1 month agoTammy
2 months agoHelene
2 months agoSherita
2 months agoWillie
2 months agoGracia
3 months agoNelida
3 months agoDiego
3 months agoDorothea
3 months agoCaitlin
4 months agoTemeka
4 months agoBulah
4 months agoRolande
4 months agoPaz
5 months agoSamuel
5 months agoBillye
5 months agoMarquetta
5 months agoTerrilyn
6 months agoRebeca
6 months agoBelen
6 months agoBrianne
6 months agoRhea
7 months agoKristel
7 months agoDaisy
7 months agoKatina
7 months ago