12-16-2012
j_security_check is used in JSP for a FORM based authentication method.
If the login succeeds and the caller is authorized to access the secured resource, then the container uses a session-id to identify a login session for the caller from that point on. The container maintains the login session with a cookie containing the session-id. The server sends the cookie back to the client, and as long as the caller presents this cookie with subsequent requests, then the container will know who the caller is.
If the login fails, then the server sends back the page identified by the form-error-page setting.
---------- Post updated at 15:59 ---------- Previous update was at 15:36 ----------
Further Reference:
JSP Security
This User Gave Thanks to Yoda For This Post:
10 More Discussions You Might Find Interesting
1. AIX
When using PowerVM Express and IVM (no HMC) on a Power6 P520 , can I configure 2 LPARs in addition to a VIO server, or does the VIO Server count as one of the two LPAR's that PowerVM Express allows? (1 Reply)
Discussion started by: JodyTek
1 Replies
2. AIX
Hi everyone,
Sorry if this post is in the wrong place. I searched the forums for "IVM" and it turned up no results. Hopefully someone knows about this. My dilemma is that I have multiple IBM JS12 Express blades in our blade center, each running VIOS 2.1.0.10-FP-20.1 and hosting a couple LPARs. Out... (2 Replies)
Discussion started by: need2bageek
2 Replies
3. AIX
Hi all please give me a link for IBM PowerVM (4 Replies)
Discussion started by: babinlonston
4 Replies
4. AIX
Hello,
Lets say for simplicity that I do not use any vlan config inside my server - one lpar group use hea physical port1, another group hea physical port2. Physical port1 configured as vlan1 on external switch, physical port2 as vlan2.
What is the common practice - should I isolate my vios... (0 Replies)
Discussion started by: vilius
0 Replies
5. AIX
Hello,
I installed PowerVM IVM Virtual I/O on P-550 but later found out that the machine isn't activated for CoD VET code for virtualization.
So when booted , it goes into OPEN Firmware
I/O Hosting requires a hosting partition boot not permitted exit called
> ok
Panel shows > IO... (3 Replies)
Discussion started by: filosophizer
3 Replies
6. AIX
I am facing problems in moving CD-ROM from one lpar to another.
CDROM can be seen on the POWERVM (IVM) server , but through the web-access if I move it ( assign it ) to LPAR it will be assigned. I run cfgmgr , and the cdrom does not show up in the LPAR. I firmly believe this is the reason why I... (2 Replies)
Discussion started by: filosophizer
2 Replies
7. AIX
Hi All,
I have a p520 box running 3 LPARs, 1 x VIOS, 1 x AIX 6.1 and 1 x AIX 7.1 and no HMC, all configuration is performed via VIOS/IVM
Until recently the box did not have the AIX7.1 LPAR and everything was fine with the box.
We needed to use AIX 7.1 for a new project, so I created a... (11 Replies)
Discussion started by: KevB
11 Replies
8. AIX
coming from this thread: https://www.unix.com/aix/211107-ibm-power-pseries-open-firmware-boot-vios-powervm-vet-code.html
PowerVM, formerly known as Advanced Power Virtualization (APV), is a chargeable feature of IBM POWER5, POWER6, POWER7, POWER8, and POWER9 servers and is required for support... (0 Replies)
Discussion started by: filosophizer
0 Replies
9. AIX
Hello,
After installing on P6 which is POWERVM IVM VIOS enabled (VET CODE D21C77ACD9229817CA1F00002C10004164 )
i get this message
"I/O hosting requires a hosting partition - boot not permitted".
HMC was connected to the machine
then HMC was removed through ASMI
Searching on... (2 Replies)
Discussion started by: filosophizer
2 Replies
10. AIX
hello
P6 was managed by HMC, tried to install on it VIOS 2.2.6
and got this error message
Hosting requires a hosting partition -- boot not permitted
vios-4 - imgbb.com
then after creating an lpar in HMC got this message
B2001230
vios-3 - imgbb.com
anyone know how to solve this... (3 Replies)
Discussion started by: filosophizer
3 Replies
LEARN ABOUT MOJAVE
setlogin
GETLOGIN(2) BSD System Calls Manual GETLOGIN(2)
NAME
getlogin, setlogin -- get/set login name
SYNOPSIS
#include <unistd.h>
char *
getlogin(void);
int
setlogin(const char *name);
DESCRIPTION
The getlogin() routine returns the login name of the user associated with the current session, as previously set by setlogin(). The name is
normally associated with a login shell at the time a session is created, and is inherited by all processes descended from the login shell.
(This is true even if some of those processes assume another user ID, for example when su(1) is used.)
setlogin() sets the login name of the user associated with the current session to name. This call is restricted to the super-user, and is
normally used only when a new session is being created on behalf of the named user (for example, at login time, or when a remote shell is
invoked).
RETURN VALUES
If a call to getlogin() succeeds, it returns a pointer to a null-terminated string in a static buffer. If the name has not been set, it
returns NULL. If a call to setlogin() succeeds, a value of 0 is returned. If setlogin() fails, a value of -1 is returned and an error code
is placed in the global location errno.
ERRORS
The following errors may be returned by these calls:
[EFAULT] The name parameter gave an invalid address.
[EINVAL] The name parameter pointed to a string that was too long. Login names are limited to MAXLOGNAME (from <sys/param.h>)
characters, currently 12.
[EPERM] The caller tried to set the login name and was not the super-user.
SEE ALSO
setsid(2)
BUGS
Login names are limited in length by setlogin(). However, lower limits are placed on login names elsewhere in the system (UT_NAMESIZE in
<utmp.h>).
In earlier versions of the system, getlogin() failed unless the process was associated with a login terminal. The current implementation
(using setlogin()) allows getlogin to succeed even when the process has no controlling terminal. In earlier versions of the system, the
value returned by getlogin() could not be trusted without checking the user ID. Portable programs should probably still make this check.
HISTORY
The getlogin() function first appeared in 4.4BSD.
4.2 Berkeley Distribution June 9, 1993 4.2 Berkeley Distribution