26 Jun, 2015
1 commit
-
This patch (thanks, Guillaume) builds appropriate Javadoc, and updates the documentation to match the changed implementation. It requires the use of -Pforgerock-release when installing and building the site in order to build the Javadoc. This patch also moves openig-doc-samples to openig-doc because the module handles both samples and Javadoc. git-svn-id: https://svn.forgerock.org/openig/trunk@1058 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
18 Jun, 2015
3 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@1055 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
Replace the field session with some getter/setter that delegates to the put/get methods from the Map interface. git-svn-id: https://svn.forgerock.org/openig/trunk@1050 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
Make the field private and add a getter. git-svn-id: https://svn.forgerock.org/openig/trunk@1048 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
15 Jun, 2015
1 commit
-
git-svn-id: https://svn.forgerock.org/openig/trunk@1040 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
11 Jun, 2015
3 commits
-
* Diamond operator * Try with resources * Multi-catch git-svn-id: https://svn.forgerock.org/openig/trunk@1035 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@1034 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
Provide through the global heap an instance of the TimeService, thus that can be shared between all the heap objects. git-svn-id: https://svn.forgerock.org/openig/trunk@1033 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
26 May, 2015
3 commits
-
is unchecked exception. git-svn-id: https://svn.forgerock.org/openig/trunk@1027 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@1026 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@1025 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
13 May, 2015
1 commit
-
git-svn-id: https://svn.forgerock.org/openig/trunk@1006 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
07 May, 2015
1 commit
-
git-svn-id: https://svn.forgerock.org/openig/trunk@1004 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
03 May, 2015
1 commit
-
…ion which are now in forgerock-util 2.0.0 git-svn-id: https://svn.forgerock.org/openig/trunk@998 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
01 May, 2015
2 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@997 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
As a best practice and as response.getStatus() may return null, it is better to swap the operand when testing equality. git-svn-id: https://svn.forgerock.org/openig/trunk@996 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
30 Apr, 2015
1 commit
-
Since we introduce the class Status in forgerock-http-framework, some code's modifications have to be done : - To get the code of the status we now have to do response.getStatus().getCode() into of response.getStatus(). (in the Groovy script or EL expression that means we'll have to write response.status.code. - Furthermore, the attribute reason in Response does not exist any more, so it is not possible anymore to assign a custom reason phrase, as it is set to standardized reason phrase through the constants defined in the class Status. - Any status code has to be in the range [100,1000[ git-svn-id: https://svn.forgerock.org/openig/trunk@994 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
27 Apr, 2015
1 commit
-
git-svn-id: https://svn.forgerock.org/openig/trunk@990 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
25 Apr, 2015
1 commit
-
* Fix the build * Upgrade to new `Promise` API * `json-fluent` also updated because it also has a dependency on forgerock-util:2.0 (`Function`) git-svn-id: https://svn.forgerock.org/openig/trunk@983 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
23 Apr, 2015
1 commit
-
git-svn-id: https://svn.forgerock.org/openig/trunk@978 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
16 Apr, 2015
1 commit
-
git-svn-id: https://svn.forgerock.org/openig/trunk@967 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
23 Mar, 2015
2 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@925 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@924 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
06 Mar, 2015
2 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@914 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
Registration and Discovery, the OAuth2Client package should be modified: the OAuth2Provider has been decoupled from the OAuth2ClientFilter and it manages now all interactions with the Authorization Server(AS). The providerHandler in the OAuth2Provider configuration become optional and if it is not specified, it use a default ClientHandler wrapping the default HTTPClient. git-svn-id: https://svn.forgerock.org/openig/trunk@913 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
25 Feb, 2015
2 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@911 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@910 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
17 Feb, 2015
1 commit
-
The type of an Expression is now given at the creation time, which means we do not provide it anymore for the evaluation. Furthermore, it helps the developper as it knows the expected type of an Expression. git-svn-id: https://svn.forgerock.org/openig/trunk@897 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
09 Feb, 2015
4 commits
-
`HttpClient` is closing the `exchange.response` object before executing the request. When the `OAuth2ClientFilter` populates the `user_info` attribute (requesting user's profile on the AS), or communicate with the AS, it reuses the `Exchange`, change the request object, but keep the response reference. So, when the modified exchange goes through `HttpClient`, any existing response gets emptied. This fix simply nullify the `exchange.response` reference *before* sending that to the AS. That prevents `HttpClient` to cleanup the response too eagerly. git-svn-id: https://svn.forgerock.org/openig/trunk@891 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@890 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@886 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@885 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
03 Feb, 2015
1 commit
-
The soon-to-come Http framework needs a subset of the features provided by `Json`: only what is related to JSON parsing/writing. Everything else is related to `JsonValue` or more OpenIG specific types like `Heap`, `Expression`, ... So this is just a simple split, we now have: * `Json`: JSON parsing * `JsonValues`: OpenIG-related code git-svn-id: https://svn.forgerock.org/openig/trunk@872 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
29 Jan, 2015
1 commit
-
if doable, the expression string input. As OPENIG-394 introduces the original string used in Expression, we are now able to have more explicit error messages. - 'Standardized' all expressions error messages. git-svn-id: https://svn.forgerock.org/openig/trunk@865 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
16 Jan, 2015
1 commit
-
The toString() method is now implemented and tested. We also decide to replace Expression constructor by a more conventional valueOf(...) factory method. A new Expression is now created by Expression exp = Expression.valueOf(<Expression string>); git-svn-id: https://svn.forgerock.org/openig/trunk@834 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
08 Dec, 2014
1 commit
-
Recent Google OAuth 2.0 update is breaking the OAuth 2.0 Client Filter by having the `expires_in` attribute of the access token response expressed as a String instead of a JSON Number. We're now doing the adaptation in OpenIG and deal with the String case by hand. git-svn-id: https://svn.forgerock.org/openig/trunk@801 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
02 Dec, 2014
1 commit
-
`ConsoleLogSink` is now rendering each `LogEntry` on 2 lines with a line separator between entries, the objective being to improve console log readability. The first line is the header line and display the timestamp of the event (in the current system Locale), the entry's `LogLevel` and ends with the `Name` (leaf part) of the heap object that is the source of the log statement. ``` MON DEC 01 20:39:16 CET 2014 (INFO) _Router Added route 'oauth2-resources.json' defined in file '/Users/guillaume/tmp/demo/config/routes/oauth2-resources.json' ------------------------------ ``` Notice that a special treatment is done when logging a `Throwable`: a condensed stack trace is printed on the console and if (and only if) the `LogSink` has been assigned a `DEBUG` or `TRACE` level, the full stack trace is printed (independently of the entry's level). ``` MON DEC 01 15:28:10 CET 2014 (DEBUG) ResourceServer Initial token resolution has failed [ OAuth2TokenException] > Initial token resolution has failed [ OAuth2TokenException] > Authorization Server returned an error (error: bad_request, description: Could not read token in CTS) org.forgerock.openig.filter.oauth2.OAuth2TokenException: Initial token resolution has failed at org.forgerock.openig.filter.oauth2.cache.CachingAccessTokenResolver.resolve(CachingAccessTokenResolver.java:62) ... 33 more ------------------------------ ``` A new `stream` property has been added to `ConsoleLogSink` to let the user choose which PrintStream to use for printing messages: * `ERR`: Use System.err (default value, keep compatibility) * `OUT`: Use System.out * `AUTO`: Select System.out for `TRACE` to `INFO` messages, switching to System.err for `WARNING` and `ERROR`. `FileLogSink` implements a machine parseable `LogEntry` rendering: each entry is on one line and includes: * timestamp of the event (in the current system Locale), always have the same length * the entry's `LogLevel`, always 1 word, uppercase * the `Name` (leaf part) of the heap object that is the source of the log statement. * a `---` separator that segregates the beginning of the line (log statement's context) from the entry's message (the rest of the line) Notice that in the case of `Throwable` printing, the full stack trace is printed as commented lines. ``` MON DEC 01 17:46:21 CET 2014 DEBUG ResourceServer --- Initial token resolution has failed # org.forgerock.openig.filter.oauth2.OAuth2TokenException: Initial token resolution has failed # at org.forgerock.openig.filter.oauth2.cache.CachingAccessTokenResolver.resolve(CachingAccessTokenResolver.java:62) # at org.forgerock.openig.filter.oauth2.OAuth2ResourceServerFilter.filter(OAuth2ResourceServerFilter.java:205) # at org.forgerock.openig.decoration.capture.CaptureFilter.filter(CaptureFilter.java:62) ``` git-svn-id: https://svn.forgerock.org/openig/trunk@771 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
21 Nov, 2014
2 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@744 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
Issues an `invalid_request` when there are multiple `Authorization` headers. Issues an `invalid_token` when there is no bearer token and when the token can't be resolved (for any reason: expiration, revocation, plain wrong token, ...) git-svn-id: https://svn.forgerock.org/openig/trunk@743 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
20 Nov, 2014
1 commit
-
The Client filter heavily use the `exchange.request.uri` property to compute URIs. That was causing issues because, in the set of upstream filters/handlers, someone could have rebased the request URI (usually to globally 'redirect' the message to the protected application). That was causing wrong URI computations (like an OAuth2 `redirect_uri` with the hostname of the protected application, instead of the user-facing one of OpenIG). This changes fix this behaviour with the introduction of an immutable `exchange.originalUri` property that is the original request URI, as received by the web container. The Client filter is now using this instead of the mutable one (`exchange.request.uri`). Updated the Nascar page sample of the documentation to limit copy/paste errors. git-svn-id: https://svn.forgerock.org/openig/trunk@735 dbb9e58e-28e6-4ce0-90e8-f11d9605b710