Wiki source code of org.clazzes.login.http
Last modified by christoph_lechleitner@iteg_at on 2013-02-02 05.21:47
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
| |
1.1 | 1 | The http-login-service org.clazzes.login.http is provided as an OSGi bundle, which may be activated by |
| 2 | |||
| 3 | (% class="code" %) | ||
| 4 | ((( | ||
| 5 | obr:addurl http:~/~/maven.clazzes.org/repository.xml | ||
| 6 | obr:deploy http-login-service | ||
| 7 | ))) | ||
| 8 | |||
| 9 | The maven artifact is: | ||
| 10 | |||
| 11 | (% class="code" %) | ||
| 12 | ((( | ||
| 13 | <groupId>org.clazzes.login</groupId> | ||
| 14 | <artifactId>http-login-service</artifactId> | ||
| 15 | ))) | ||
| 16 | |||
| 17 | === {{id name="org.clazzes.login.http-Functionality"/}}Functionality === | ||
| 18 | |||
| 19 | The HTTP login service authenticates against users in a configured domain using the scheme described in [[doc:LOGIN.DomainPasswordLoginService implementations and backends.org\.clazzes\.login\.http.HTTP authentication API NG.WebHome]]. | ||
| 20 | |||
| 21 | === {{id name="org.clazzes.login.http-Configuration"/}}Configuration === | ||
| 22 | |||
| 23 | The HTTP login service may be configured using the OSGi configuration PID {{code language="none"}}org.clazzes.login.http{{/code}} using these configuration values: | ||
| 24 | |||
| 25 | |=((( | ||
| 26 | (% class="tablesorter-header-inner" %) | ||
| 27 | ((( | ||
| 28 | Key | ||
| 29 | ))) | ||
| 30 | )))|=((( | ||
| 31 | (% class="tablesorter-header-inner" %) | ||
| 32 | ((( | ||
| 33 | Description | ||
| 34 | ))) | ||
| 35 | ))) | ||
| 36 | |((( | ||
| 37 | {{code language="none"}} | ||
| 38 | defaultDomain | ||
| 39 | {{/code}} | ||
| 40 | )))|((( | ||
| 41 | The domain to use for principals, which do not contain a domain. | ||
| 42 | ))) | ||
| 43 | |((( | ||
| 44 | {{code language="none"}} | ||
| 45 | domain.<domain>.controllerUri | ||
| 46 | {{/code}} | ||
| 47 | )))|((( | ||
| 48 | The server to contact. Supported URL schemes: {{code language="none"}}https{{/code}}, {{code language="none"}}http{{/code}}. | ||
| 49 | ))) | ||
| 50 | |((( | ||
| 51 | {{code language="none"}} | ||
| 52 | domain.<domain>.bindUser | ||
| 53 | {{/code}} | ||
| 54 | )))|((( | ||
| 55 | The user used for HTTP basic authentication before doing the actual authentication. If empty, no basic auth is performed. | ||
| 56 | ))) | ||
| 57 | |((( | ||
| 58 | {{code language="none"}} | ||
| 59 | domain.<domain>.bindPassword | ||
| 60 | {{/code}} | ||
| 61 | )))|((( | ||
| 62 | The password used for HTTP basic authentication before doing the actual authentication. If empty, no basic auth is performed. | ||
| 63 | ))) | ||
| |
2.1 | 64 | |((( |
| 65 | {{code language="none"}} | ||
| 66 | domain.<domain>.useJson | ||
| 67 | {{/code}} | ||
| 68 | )))|((( | ||
| 69 | If set to "{{code language="none"}}1{{/code}}", the JSON variant of the backend interface is used providing {{code language="none"}}prettyName{{/code}} fields. Supported since {{code language="none"}}1.2.0{{/code}}. | ||
| 70 | ))) | ||
| |
1.1 | 71 | |
| 72 | There might be multiple domains in a configuration. | ||
| 73 | |||
| 74 | The term "domain" refers to a login domain, not a DNS domain. |