Protecting Java EE Applications With OpenSSO Policy Agents, Part 2: Same-Domain SSO


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS Protecting Java EE Applications With OpenSSO Policy Agents, Part 2: Same-Domain SSO
# 1  
Old 01-08-2009
Protecting Java EE Applications With OpenSSO Policy Agents, Part 2: Same-Domain SSO

See how to configure OpenSSO so that certain resources on your secured application are publicly accessible, with no authentication required. Also included is an overview of the types of single sign-on.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Programming

Java Applications and Xterm

I spent a ton of time developing a java application as an interface to a unix file system. We use xterm and I use a lot of swing elements to make the interface user friendly. The user will start the java application from the command-line in xterm and the application opens in its own JFrame. ... (1 Reply)
Discussion started by: nwboy74
1 Replies
Login or Register to Ask a Question
ABRT-ACTION-ANALYZ(1)						    ABRT Manual 					     ABRT-ACTION-ANALYZ(1)

NAME
abrt-action-analyze-java - Calculate and save UUID & DUPHASH and determine the level of usability for reporting of a Java stack trace. SYNOPSIS
abrt-action-analyze-java [-v] [-d DIR] [-o] [-f FILE] DESCRIPTION
The tool reads the file named backtrace from a problem data directory, processes it and generates a universally unique identifier (UUID). Then it saves this data as new element uuid. It also checks whether the stack trace contains a remote address in any of its frames and if so it creates not-reportable element whose contents explains why the stack trace should not be reported into a bug tracking system. Integration with ABRT events abrt-action-analyze-java can be used to generate the UUID & DUPHAS of a newly saved Java stack trace. EVENT=post-create analyzer=Java abrt-action-analyze-java OPTIONS
-d DIR Path to a problem directory. The tool reads the backtrace from stdin when neither this option nor -f is provided. -f FILE Path to a stack trace. The tool reads the backtrace from stdin when neither this option nor -d is provided. -o Print the result to stdout. -v Be more verbose. Can be given multiple times. AUTHORS
o ABRT team abrt-java-connector 01/19/2014 ABRT-ACTION-ANALYZ(1)