03 Dec, 2014
1 commit
-
git-svn-id: https://svn.forgerock.org/openig/trunk@777 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
02 Dec, 2014
7 commits
-
Reviewed onscreen by Jean-Charles. git-svn-id: https://svn.forgerock.org/openig/trunk@776 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@775 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@774 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@773 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
`HeapImpl.addDefaultDeclaration()` is now the way to add default object declarations in the heap. Default declarations are only included if no user-provided overriding declaration is found (only works for heap declarations, not for named inline declaration). git-svn-id: https://svn.forgerock.org/openig/trunk@772 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
`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 -
git-svn-id: https://svn.forgerock.org/openig/trunk@770 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
01 Dec, 2014
4 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@769 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
Minor updates reviewed by Guillaume The expectation is that OpenIG will expose endpoints like this under /openig. git-svn-id: https://svn.forgerock.org/openig/trunk@768 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
contains a port number. git-svn-id: https://svn.forgerock.org/openig/trunk@767 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
Indeed, the host http header wasn't replaced when doing a rebaseUri, but not only in this case, with the setUri too. To solve this problem, a simple fix would be to do an update of the headers when getting them. - A unit test has been added for the DispatchHandler case. git-svn-id: https://svn.forgerock.org/openig/trunk@766 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
28 Nov, 2014
9 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@765 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@764 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@763 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@762 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
The decorations are now applied in a more intuitive way: * Local decorations are declared inside of the heap object declaration (no changes here) ``` { "type": "Something", "decorator-name": "configuration ..." } ``` * Global decorations are declared in a top-level element called `globalDecorators` and are inherited by sub-heap. ``` "globalDecorators": { "decorator-name": "configuration ...", ... } ``` * Top-level handler decorations are declared as top-level attributes ``` "handler": "NameOfHandler" "decorator-name": "configuration ..." ``` Decorators are applied in this order: 1. local decorations 2. global decorations (inherited first, up to the ones declared in the requester heap) 3. top-level reference decorations (only if the heap object is the main `handler` object and retrieved with `HeapImpl.getHandler()`) Default configuration is now using the top-level reference decoration style. git-svn-id: https://svn.forgerock.org/openig/trunk@761 dbb9e58e-28e6-4ce0-90e8-f11d9605b710 -
This audit framework application maintains hit counters on a per-tag basis. Here is an output sample: ``` { "resources": { "completed": 1, "failed": 0, "flowing": 0 }, "main": { "completed": 12, "failed": 0, "flowing": 1 }, "monitor": { "completed": 11, "failed": 0, "flowing": 1 } } ``` `resources`, `main` and `monitor` being "non-standard" (or user-provided) tags. git-svn-id: https://svn.forgerock.org/openig/trunk@760 dbb9e58e-28e6-4ce0-90e8-f11d9605b710 -
git-svn-id: https://svn.forgerock.org/openig/trunk@759 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@758 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
The `307` status code is a temporary redirect and is processed by the UA as a complete request replay (including method, form params, ...). `302`, on the other hand simply expects the UA to `GET` the provided `Location` Uri value. git-svn-id: https://svn.forgerock.org/openig/trunk@757 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
27 Nov, 2014
3 commits
-
Reserve real usage of HttpServletRequest and HttpServletResponse objects for Fedlet classes only. Session attributes' variables `subjectMapping`, `sessionIndexMapping`, `authnContext` and all of the `attributeMapping` values are now stored in the OpenIG Session object (instead of the `HttpSession`). That makes it possible to use theses values inside OpenIG configuration files (through `Expression`). git-svn-id: https://svn.forgerock.org/openig/trunk@756 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@755 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
The issue was due to the BeanELResolver involded by the use of Expression which was unable to get the right setter to set the URI. Solution was to create a RequestResolver, to guide it through the setters to get the right one and to finally be able to write the uri as expected. - added RequestResolver.class - added unit tests for the new RequestResolver class. - added unit tests for the AssignmentFilter about URI change. Thanks to Guillaume for his help. git-svn-id: https://svn.forgerock.org/openig/trunk@754 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
26 Nov, 2014
1 commit
-
Additional fix suggested and reviewed by Guillaume over IM git-svn-id: https://svn.forgerock.org/openig/trunk@752 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
25 Nov, 2014
5 commits
-
Now that we have a CaptureDecorator to capture the exchange, we do not need to document a script for doing the same thing. In working on this issue, it also became apparent that these examples did not call for dumping the exchange anyway. git-svn-id: https://svn.forgerock.org/openig/trunk@751 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
A SamlFederationHandler maps data from the assertion into the exchange.session object. With multiple SP configurations, it is important to use unique field names for mapped data to avoid one handler from overwriting another's session data. This patch fixes the doc to account for that requirement. git-svn-id: https://svn.forgerock.org/openig/trunk@750 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
This patch anticipates the release of OpenAM 12. I'm hoping that http://sources.forgerock.org/browse/openam/trunk/openam/pom.xml?hb=true#to123 does not change before release. git-svn-id: https://svn.forgerock.org/openig/trunk@749 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@748 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@747 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
24 Nov, 2014
1 commit
-
git-svn-id: https://svn.forgerock.org/openig/trunk@746 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
22 Nov, 2014
1 commit
-
git-svn-id: https://svn.forgerock.org/openig/trunk@745 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
21 Nov, 2014
3 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
-
git-svn-id: https://svn.forgerock.org/openig/trunk@742 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
20 Nov, 2014
5 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@741 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
…nsure that invalid JWT sessions are expired git-svn-id: https://svn.forgerock.org/openig/trunk@740 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
Timer values should always be obtained through `timer` decorations. git-svn-id: https://svn.forgerock.org/openig/trunk@739 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@738 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
This patch adds an appendix that briefly describes and demonstrates how OpenIG as a SAML 2.0 SP can support more than one application. For future consideration I have also opened some issues that might make this easier: OPENIG-397, but also OPENIG-399, OPENIG-400. git-svn-id: https://svn.forgerock.org/openig/trunk@737 dbb9e58e-28e6-4ce0-90e8-f11d9605b710