About
  • This user has not yet committed.

Reviews

13 active reviews

Counts may include data that you cannot access.

tim

EarlieractivityNolateractivity
tim

commented on OPENAM-751

27 Jan
Agreed, it should be disabled by default, but is useful for debugging, especially if it also contains "DAS" for the Dist Auth module. I would suggest therefore there is an advanced property to turn it on.
tim

created OPENAM-766

28 Jul 11
tim

changed the Summary to 'REST interface needs to be configurable for restrictions' on OPENAM-763

27 Jul 11
tim

created OPENAM-763, COMMWEB-31

27 Jul 11
tim

closed COMMWEB-7

13 Jun 11
tim

updated the Environment of OPENAM-638

26 May 11
tim

commented on CR-208

18 May 11

As this is such a tiny change - why was non-cdsso excluded in the first place? For any good reason?

tim

closed OPENAM-469

17 May 11
At the present time neither we nor Andreas can reproduce the problem.
tim

created OPENAM-623, OPENAM-610

29 Apr 11
tim

updated 3 fields of OPENAM-480

13 Apr 11
tim

commented on CR-184

07 Apr 11

Looks ok to me but I am not familiar with the code. As this affects only notifications then I suppose the chance of unintended behaviour is small?

tim

commented on OPENAM-480

23 Mar 11
Chris, could you let me know if restarting the servers during your scripted installation after configuring the site is a valid workaround for you? I believe this is the case and it would be good to confirm it. We will also evaluate Andreas's patch.
tim

commented on OPENAM-480

17 Mar 11
I believe this issue occurs only when adding a site but not restarting OpenAM.

Please could you test this and let me know if that resolves the problem?

It's not clear which config changes require a restart, but adding a site or amending site details is certainly one of them at the moment. I will open an RFE for documenting this more clearly, and longer term we will look at those outstanding areas where restarts are required and eliminate them.
tim

created OPENAM-577, OPENAM-576, OPENAM-569

16 Mar 11
tim

commented on OPENAM-480

11 Mar 11
This has been reported again - can you confirm it is still an issue and that you didn't find the cause? Thanks.
tim

changed the Assignee to 'Tim Rault-Smith' on OPENAM-480

11 Mar 11
tim

changed the Case Id to 'WVR-834448 XWC-442632' on OPENAM-447

07 Feb 11
tim

closed COMMWEB-22, COMMWEB-9

31 Jan 11
tim

resolved COMMWEB-22

03 Jan 11
Good suggestion, Peter. Your wish is our command.
tim

commented on COMMWEB-9

03 Jan 11
Closing as not a bug, and assuming no further trouble since no updates since May.
tim

changed the Case Id to 'FWI-930783, LHI-954171' on OPENAM-329

30 Dec 10
tim

closed COMMWEB-17

09 Oct 10
Issue resolved, no further comments, closing.
tim

resolved COMMWEB-17

20 Sep 10
Pretty sure the double issue in the URL is down to Gmail. Will close at the end of the week if no further updates.
tim

commented on COMMWEB-17

20 Sep 10
Also, which mail client are you using? I didn't see this before on an IMAP server, but checking on Google Mail in the web interface I see it - I have a feeling it may be the mail client that's putting in the links based on the text it finds. JIRA appears to be sending out plain text mails, in which case this may be nothing to do with JIRA at all.

(Andreas, I notice you have a gmail address...)
tim

commented on COMMWEB-17

20 Sep 10
I am still looking into this. Please could you confirm whether you are seeing the following:

The issue number of the next issue in the list is being appended to the URL for the previous issue, but ONLY for issue IDs > 100?

Here is an example of a mail I just received:

OPENAM-254 IDP breaks in a load-balanced environment (NullPointerException at com.sun.identity.saml2.profile.IDPSSOUtil.getAssertion)
           https://bugster.forgerock.org/jira/browse/OPENAM-254
OPENAM-251 Begining with OpenAm
           https://bugster.forgerock.org/jira/browse/OPENAM-251
OPENAM-249 Not possible to create a password reset servcie without secret questions
...
           https://bugster.forgerock.org/jira/browse/OPENAM-103
OPENAM-95 ServiceConfigManagerImpl cache always returns stale cache instance even after admin token refresh
           https://bugster.forgerock.org/jira/browse/OPENAM-95
OPENAM-93 redirect to top level realm after session timeout
           https://bugster.forgerock.org/jira/browse/OPENAM-93
...

The links are wrong from the second in the list up to issue OPENAM-103, which is the last 3-digit issue in my list, but from OPENAM-95 onwards it is correct. I deduce that it is the 3-digit issue IDs which trigger the problem.
tim

closed COMMWEB-16, COMMWEB-13

06 Sep 10
tim

changed the Link to 'This issue duplicates COMMWEB-13' on COMMWEB-17

06 Sep 10
tim

changed the Link to 'This issue is duplicated by COMMWEB-17' on COMMWEB-13

06 Sep 10
tim

changed the Link to 'This issue duplicates COMMWEB-16' on COMMWEB-17

06 Sep 10
tim

changed the Link to 'This issue is duplicated by COMMWEB-17' on COMMWEB-16

06 Sep 10