AuthenticationObjects must be permanent in order to be useful. If an AuthenticationObject is destroyed, its associated LOID, which identifies the user to the rest of the system, is lost. There is no way to generate an identical LOID for a new AuthenticationObject.
$ legion_login /users/nemo -e legion_ping -c /home/nemo/bob Password: xxxx Bob's here. $
$ legion_cat /home/nemo/bob Legion ExoEvent Caught: Type : "Exception:Security:MayI" Description : "Security fault, MayI failed" Source Loid : 1.3622a3eb.06.9bb12a36.000001fc... Destination Loid : 1.3622a3eb.66000000.04000000.000... Function Id : _i_16exportsInterface_21LegionObjectInterface_V $
You can now add users to your system, by creating user ids. A user id is an entry in context space that represents an AuthenticationObject. It is also used to signify ownership of all objects that a logged in user creates. The admin creates user ids with the legion_create_user command. This command will also create a home context for the new user. To create a user id for "nemo," for example, you would enter:
$ legion_create_user nemo New Legion password: xxxx Retype password: xxxx 1.3622a3eb.6b000000.03000000.000001fc... Creating a Home context: /home/nemo Creating context "nemo" in parent "/home". New context LOID = "1.3622a3eb.05.11000000.000001fc..." Changing ACLs on /home/nemo $
The legion_create_user command is actually a simple wrapper around legion_create_user_object. The full command can give more control to the creation of AuthenticationObjects; execute it without arguments for a summary of its options.
Once a user is created, log in is achieved by giving the context path of the user object and a password to legion_login.
$ legion_login /users/nemo Password:xxxx $