org.forgerock / org.forgerock.openidm

08 Jan, 2013

1 commit

11 Dec, 2012

1 commit

29 Nov, 2012

1 commit

28 Nov, 2012

1 commit

  • 014a8fe0   merging ui branch r1634-1654 ... Browse Dir » 
    Using new validateOnlyIfPresent flag to solve https://bugster.forgerock.org/jira/browse/OPENIDM-934 

Modifying apache configuration to reverse proxy for all requests to openidm/ rather than just to openidm/managed

misc trivial cleanup

git-svn-id: https://svn.forgerock.org/openidm/trunk@1656 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    jake.feasel
     

20 Nov, 2012

2 commits

19 Nov, 2012

1 commit

15 Nov, 2012

1 commit

  • f5fe64ad   UI branch changes, r1480-1529 ... Browse Dir » 
    http://sources.forgerock.org/cru/CR-891

This also includes global rename of _query-id to _queryId and _query-expression to _queryExpression.

Note for documenters: there are several changes expected to be made soon; review the code review (linked above) and note Andi's comments

git-svn-id: https://svn.forgerock.org/openidm/trunk@1531 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    jake.feasel
     

12 Nov, 2012

1 commit

  • 60d0d9cf   Merging UI branch, r1455-1477 ... Browse Dir » 
    Updates for UI: Corrected policy, max security answer attempts, task/workflow updates.
http://sources.forgerock.org/cru/CR-862

git-svn-id: https://svn.forgerock.org/openidm/trunk@1485 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    jake.feasel
     

08 Nov, 2012

1 commit

02 Nov, 2012

2 commits

11 Oct, 2012

1 commit

13 Sep, 2012

1 commit

  • 26a52deb   CR-607 CR-630 ... Browse Dir » 
    - ui divided into three modules, 
- customizable forms, 
- new dashboard & apps views,
- js refactoring,
- apps request approval simple workflow,
- users table pagination 



git-svn-id: https://svn.forgerock.org/openidm/trunk@1207 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    mbilski
     

13 Mar, 2012

1 commit

  • 2daf53af   New feature COMMWEB-37: Provide maven plugin for core documentation ... Browse Dir » 
    The refactoring affects path names to HTML content. Examples:

Before
http://openam.forgerock.org/doc/admin-guide/OpenAM-Admin-Guide.html#configure-authn-chains
http://opendj.forgerock.org/doc/admin-guide/OpenDJ-Admin-Guide.html#chap-account-lockout
http://openidm.forgerock.org/doc/integrators-guide/OpenIDM-Integrators-Guide.html#security-bootstrap

After
http://openam.forgerock.org/doc/admin-guide/index.html#configure-authn-chains
http://opendj.forgerock.org/doc/admin-guide/index.html#chap-account-lockout
http://openidm.forgerock.org/doc/integrators-guide/index.html#security-bootstrap

git-svn-id: https://svn.forgerock.org/openidm/trunk@1024 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    mark
     

20 Feb, 2012

1 commit

08 Feb, 2012

1 commit

07 Feb, 2012

1 commit

26 Jan, 2012

1 commit

11 Jan, 2012

1 commit

03 Jan, 2012

1 commit

30 Dec, 2011

1 commit

09 Dec, 2011

1 commit

02 Dec, 2011

1 commit

01 Dec, 2011

1 commit

  • 745881bd   Introduce line unfolding and refolding in <screen> output for HTML ... Browse Dir » 
    The idea is that when you break long lines in <screen> at a space character, the reader can double-click to collapse folded lines to a single line for easy copying into a terminal window, and then double-click again to refold the lines for easy reading. Line continuations with \ would allow folded lines to be used directly, at least on *n*x, and also be syntactically correct. Yet, its harder to edit a command that used \ to continue lines.

The JavaScript expects line continuations where continued lines start with a space. Lines without initial spaces do not get collapsed. For example:

<screen>$ curl
 --user admin:admin
 -X PUT
 -d '{
 "name":"joe",
 "firstname":"joe",
 "lastname":"smith",
 "email":"joe@abc.com",
 "userPassword":"11111111"}'
 http://localhost:8080/openidm/managed/user/joe
{"_rev":"0","_id":"joe"}</screen>

Shows up as:

$ curl
 --user admin:admin
 -X PUT
 -d '{
 "name":"joe",
 "firstname":"joe",
 "lastname":"smith",
 "email":"joe@abc.com",
 "userPassword":"11111111"}'
 http://localhost:8080/openidm/managed/user/joe
{"_rev":"0","_id":"joe"}

And then when you double-click:

$ curl --user admin:admin -X PUT -d '{ "name":"joe", "firstname":"joe", "lastname":"smith", "email":"joe@abc.com", "userPassword":"11111111"}' http://localhost:8080/openidm/managed/user/joe
{"_rev":"0","_id":"joe"}

And vice versa.

There's no doubt cleanup to do in the core doc sources to take advantage of this.

git-svn-id: https://svn.forgerock.org/openidm/trunk@551 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    mark
     

25 May, 2011

1 commit