Re: [Architecture] Tiqr Client for IS Authenticator

Hi Shakila, Enrolment is fine. However I think we need to have some kind of reference to the enrolled user ID in tiqr to the username in IS. Otherwise how are we going to relate/know the user who has actually logged in with tiqr. All that tiqr might say is (this is what I am thinking, not yet

Re: [Architecture] Tiqr Client for IS Authenticator

Hi Johann, We can track the IS user who logged in via tiqr, if we do this via two-factor authentication (we can do basic authentication as the first factor). And I don't think, saving these mapping detail in registry would be useful for future use. Because we have to use another User ID for next

Re: [Architecture] [AF] Adding ESB Applications to App Factory

Hi all, We have completed the initial dev work related to ESB app type in App Factory. We have completed the following during the last couple of weeks. - The issue that we observed as described at the end of the previous update (looking for a JKS in a path called /root/.keystore ) was due

Re: [Architecture] [IS][Workflow] Workflow Dashboard Gadget - Operations Exposed to End User

Hi Chamila, On Tue, Nov 3, 2015 at 9:50 AM, Chamila Wijayarathna wrote: > Hi all, > > Currently IS expose a dashboard gadget where users can see and > approve/reject workflow requests assigned to him or claimable to him. > Previously we exposed following operations for

Re: [Architecture] Tiqr Client for IS Authenticator

Hi Johann, There is another method called authentication available in tiqr. If we have an enrolled tiqr user in mobile device, we can use tiqr authentication. If we don't have any pre-enrolled user in mobile device, we can't use tiqr authentication. And we can't expect the user to have an

Re: [Architecture] Tiqr Client for IS Authenticator

Hi Shakila, If you have already planned on how to achieve this, can you elaborate a little more (ideally using a diagram) on how the end user experience is going to be for enrolment and authentication flows once this authenticator is completed ? What I want to know is at which point will the

[Architecture] [IS][Workflow] Workflow Dashboard Gadget - Operations Exposed to End User

Hi all, Currently IS expose a dashboard gadget where users can see and approve/reject workflow requests assigned to him or claimable to him. Previously we exposed following operations for dashboard users. Claim, Release, Start. Stop, Approve, Reject, Suspend, Resume. >From the discussion I had

Re: [Architecture] [DAS] Java Agent to monitor server activities

Look good On Wed, Oct 28, 2015 at 1:58 PM, Udani Weeraratne wrote: > Hi, > > I am working on a java agent which can be used to monitor different > activities carried out within DAS. Main concept of java agent is to modify > bytecode of classes before they load onto JVM (bytecode