You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,21 +15,21 @@ The module doesn’t make Authentication by it self, but verify if Authenticatio
15
15
16
16
`Authentication` is made by a login form page.
17
17
18
-
This login page must authenticate the user with any authenticate source (ldap, /etc/password, file, database....) accessible to language of the page (php, perl, java... an ldap login page sample in php are in samples directory).
18
+
This login page must `authenticate` the `user` with any `authenticate source` (ldap, /etc/password, file, database....) accessible to `language` of the `page` (php, perl, java... an ldap login page sample in php are in samples directory).
19
19
20
-
Then this page must set cookie that contains only a key the `Authentication unique id` of the `Authentication session`.
20
+
Then this page must set `cookie` that contains only a key the `Authentication unique id` of the `Authentication session`.
21
21
22
-
The login page must store authorization and user information of the authenticated user in [memcached](http://memcached.org/) identified by the cookie key `Authentication unique id`.
22
+
The login page must `store` authorization and user information of the authenticated user in [`memcached`](http://memcached.org/) identified by the cookie key `Authentication unique id`.
23
23
24
-
The login page can be developed in any language you want, but must be capable to use [memcached](http://memcached.org/) (they must have memcache client api for us)
24
+
The `login page` can be developed in `any language you want`, but must be capable to use [`memcached`](http://memcached.org/) (they must have memcache client api for us)
25
25
26
26
## Phase 2 : The Apache v2 Module
27
27
28
28
After the user is logged, the Auth MemCookie module check on each protected page by apache ACL is the user is authenticated.
29
29
30
30
When authenticating a request Auth MemCookie module walks through the following steps:
31
31
32
-
1. Get the **`session id`**. The `session id` is stored in a cookie (by default named `AuthMemCookie`).
32
+
1. Get the **`session id`**. The **`session id`** is stored in a cookie (by default named `AuthMemCookie`).
33
33
34
34
2. Get the **`session data`**. Auth MemCookie module fetches **`session data`** by looking up the session id on the [memcached](http://memcached.org/) server.
0 commit comments