22 Oct, 2014

1 commit


21 Oct, 2014

1 commit

  • OPENIDM-2284
    
    Add the correlation query section on the correlation tab.  Allows user to configure query using a script or an expression tree.
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@4101 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    liz.browne
     

17 Oct, 2014

1 commit

  • CR-4871
    CR-4876
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@4078 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    liz.browne
     

16 Oct, 2014

1 commit


15 Oct, 2014

1 commit


13 Oct, 2014

1 commit


10 Oct, 2014

1 commit


09 Oct, 2014

4 commits


08 Oct, 2014

4 commits


07 Oct, 2014

1 commit


03 Oct, 2014

1 commit


30 Sep, 2014

1 commit


29 Sep, 2014

2 commits

  • OPENIDM-2219, 
    OPENIDM-2220, 
    OPENIDM-2221,
    
    Creates a new page to later be linked to from the mapping page. Allows user to configure situation policies manually or select from a list of predefined patterns. A scheduler widget was also created that is used to define recon schedules, though can be used for livesync where needed.
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@3953 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    liz.browne
     
  • git-svn-id: https://svn.forgerock.org/openidm/trunk@3950 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    huck.elliott
     

22 Sep, 2014

1 commit


19 Sep, 2014

1 commit


12 Sep, 2014

1 commit

  • OPENIDM-2177
    
    Basic Authentication Configuration for OpenIDM admin
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@3891 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    liz.browne
     

09 Sep, 2014

1 commit


08 Sep, 2014

1 commit

  • These changes add the Object Type interface for the add/edit connectors page.
    
    git-svn-id: https://svn.forgerock.org/openidm/trunk@3869 d98387aa-ee2c-4292-a9e6-504d2a719fd3
    liz.browne
     

05 Sep, 2014

1 commit


19 Aug, 2014

1 commit


14 Aug, 2014

1 commit


01 Aug, 2014

1 commit


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


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