Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
-
Objects (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. VincentMassol1 +XWiki.hungpt - Content
-
... ... @@ -8,11 +8,12 @@ 8 8 * It is not stored in the database 9 9 * It cannot be modified in any way 10 10 * It always has full access, regardless of the rights settings 11 -Because it is so powerful, it is not safe to leave it enabled for a long time. 12 12 12 +#warning("Because it is so powerful, it is not safe to leave it enabled for a long time.") 13 + 13 13 By default, this account is disabled. To enable it, you have to edit <tt><xwiki-dir>/WEB-INF/xwiki.cfg</tt>, uncomment the <tt>xwiki.superadminpassword=system</tt> line and set a proper password. To disable it, just comment this line. Remember to restart the servlet container after changing <tt>xwiki.cfg</tt>. 14 14 15 -#info("Using this superadmin account is useful when you cannot log in anymore, for example when you forgot your admin user password orif you messed upthe rights.")16 +#info("Using this superadmin account is useful when you cannot log in anymore, for example when you forgot your admin user password, if you messed up some rights or if you have deleted your admin user by mistake.") 16 16 17 17 1.1 Cookie Encryption Keys 18 18
- GHOSTERR.TXT
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.hungpt - Size
-
... ... @@ -1,0 +1,1 @@ 1 +321 bytes - Content
- XWiki.XWikiComments[0]
-
- Comment
-
... ... @@ -1,0 +1,1 @@ 1 +You shouldn't store the username and password in the cookie itself. Keep that information on the server side, hidden behind a randomly generated number. Ie. use it as the primary key in a databasetable. The random number is then stored in the users cookie. It's much safer and it does not require secrets. - Date
-
... ... @@ -1,0 +1,1 @@ 1 +2007-05-20 13:10:10.0 - Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Jersin
