18 Feb, 2015

1 commit


17 Dec, 2014

1 commit


13 Dec, 2014

1 commit


31 Oct, 2014

1 commit


28 Oct, 2014

1 commit


15 Oct, 2014

1 commit


10 Oct, 2014

1 commit


19 Sep, 2014

1 commit

  • CUI-27: Updating third party libraries in forgerock-ui
    Upgrading openidm-ui to use forgerock-ui 1.1
    Upgraded forgeorck-ui will resolve these:
    OPENIDM-2119 (A user with " or > in the username becomes unavailable to the admin)
    OPENIDM-2231 (logout button does not send automatically and immediately user back to login page) 
    Pulling in codemirror 4.5 for openidm-ui-admin
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@3920 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    jake.feasel
     

01 Aug, 2014

1 commit


29 Jul, 2014

1 commit


16 Jul, 2014

1 commit

  • r3353:3535 https://svn.forgerock.org/openidm/branches/3.1-earlyprototype
    
    
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@3537 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    brmiller
     

02 Nov, 2012

2 commits


13 Mar, 2012

1 commit

  • 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

  • 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