01 Dec, 2014
2 commits
-
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
10 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
-
The audit framework is a new OpenIG API that gives to users a deeper view (and probably a better understanding) of what's going on in the observed OpenIG system. This is an initial version of the audit framework that only supports `Exchange` flow observation: Filters and Handlers will send `AuditEvent` notifications both when an Exchange enters or exists. An `AuditEvent` is a notification that includes meta-information about the observed component emitter of the notification (its `Name` in particular), a timestamp, the exchange being captured and a set of tags that helps to qualify the event. Four tags are supported out-of-the-box: `request`, `response`, `completed` and `exception`. The user can add as many tags as wanted as part of the decoration configuration: "audit": "route-#1" // add a single tag to the decorated component "audit": [ "super-tag", "route-#2" ] // add all of theses tags "audit": boolean, object, ... // any other format will be ignored OpenIG provides a single `audit` decorator by default. Consumers of AuditEvent are `AuditEventListener`, they have to provide their own Heaplet implementation that extends `ConditionalListenerHeaplet`. They'll be automatically notified of emitted AuditEvents and can (optionally) filter the received event using the `condition` configuration attribute (condition is expressed as an `Expression` that needs to evaluate to a boolean). Examples of such event-filtering conditions: ${true} ${contains(tags, 'tag#1')} ${source.name.leaf == 'source'} git-svn-id: https://svn.forgerock.org/openig/trunk@736 dbb9e58e-28e6-4ce0-90e8-f11d9605b710 -
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
-
git-svn-id: https://svn.forgerock.org/openig/trunk@734 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
only used by the Client Server and to uniformize the message with the OAuth2ResourceFilter. git-svn-id: https://svn.forgerock.org/openig/trunk@733 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
expressions. OAuth2ResourceServerFilter.java - Replaced 'Set<String> scopes' to 'List<Expression> scopes'. - As the AccessToken defines scopes as Set<String>, added a new method to getScopes from List<Expression> to Set<String>. - InsufficientScopeChallengeHandler is no longer a field of the OAuth2ResourceServerFilter. - Added realm attribute to the OAuth2ResourceServerFilter. OAuth2ResourceServerFilterTest.java - Fixed tests according to the above modifications. - Added unit tests with expression evaluations. man-OAuth2ResourceServerFilter.xml - Modified doc according to Mark's patch. git-svn-id: https://svn.forgerock.org/openig/trunk@732 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
19 Nov, 2014
3 commits
-
* also added test to ensure that it is possible to inline a route's handler and avoid the need for a heap. git-svn-id: https://svn.forgerock.org/openig/trunk@730 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@725 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
git-svn-id: https://svn.forgerock.org/openig/trunk@724 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
18 Nov, 2014
2 commits
-
git-svn-id: https://svn.forgerock.org/openig/trunk@723 dbb9e58e-28e6-4ce0-90e8-f11d9605b710
-
Updated version of json-fluent and json-web-token from 2.3.2 to 2.4.1 new release. Thanks to Bruno! \o/ git-svn-id: https://svn.forgerock.org/openig/trunk@722 dbb9e58e-28e6-4ce0-90e8-f11d9605b710