Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

IBM Exam C9510-401 Topic 5 Question 108 Discussion

Actual exam question for IBM's C9510-401 exam
Question #: 108
Topic #: 5
[All C9510-401 Questions]

A web application has a configured session timeout of eight hours and a default LTPA token timeout of two hours. After every two hours, the users have to log in again from their HTTP browser. The system administrator is required to make configuration changed so users only have to log in once, while keeping the above mentioned timeouts the same. The authentication mechanism available is Kerberos.

How should the administrator do this?

Show Suggested Answer Hide Answer
Suggested Answer: B

In WebSphere Application Server Version 6.1, a trust association interceptor (TAI) that uses the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) to securely negotiate and authenticate HTTP requests for secured resources was introduced. This function was deprecated In WebSphere Application Server 7.0. SPNEGO web authentication has taken its place to provide dynamic reload of the SPNEGO filters and to enable fallback to the application login method.

References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/csec_ssovo.html


Contribute your Thoughts:

Virgina
1 months ago
I think we should go with SPNEGO, it seems to be the most appropriate solution.
upvoted 0 times
...
Troy
1 months ago
I see your point, Troy. But SPNEGO is specifically designed for this kind of scenario.
upvoted 0 times
...
Colette
1 months ago
Haha, with 8 hour session timeouts, users will be logging in more often than they change their socks! I'd go with B for the SPNEGO option.
upvoted 0 times
Donette
18 days ago
User 3: Definitely, it's a good solution for this situation.
upvoted 0 times
...
Mi
24 days ago
User 2: Yeah, it should help reduce the number of logins.
upvoted 0 times
...
Deane
25 days ago
User 1: I agree, SPNEGO sounds like the way to go.
upvoted 0 times
...
...
Troy
1 months ago
I'm not sure, but I think C) Enable Session Management Security Integration could also work.
upvoted 0 times
...
Virgina
1 months ago
I agree with Troy, SPNEGO is the way to go for single sign-on.
upvoted 0 times
...
Alfred
1 months ago
D. Enabling Web Inbound security attribute propagation sounds like the right solution to me. That way, the session token would be shared across the application.
upvoted 0 times
...
Daniela
2 months ago
I think the answer is B. SPNEGO Web or SPNEGO TAI would allow users to authenticate once and not have to log in again.
upvoted 0 times
Kanisha
16 days ago
The administrator should definitely look into implementing SPNEGO Web or SPNEGO TAI for a smoother authentication process.
upvoted 0 times
...
Micaela
17 days ago
Definitely, it would improve user experience and reduce the need for frequent logins.
upvoted 0 times
...
Marylin
26 days ago
That makes sense. It would simplify the login process for users.
upvoted 0 times
...
Filiberto
27 days ago
B) Configure the SPNEGO Web or SPNEGO TAI.
upvoted 0 times
...
...
Troy
2 months ago
I think the answer is B) Configure the SPNEGO Web or SPNEGO TAI.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77