AnsweredAssumed Answered

Active Directory - Introscope Integration

Question asked by JKW on Nov 20, 2012
Latest reply on Nov 20, 2012 by JKW
I have Introscope integrated with Active Directory. Users are able to login and are granted priveledges based on the domains.xml file.

However, if I utilize the Java Console to check for errors, when a user logs in using an integrated Active Directory account, the following error is given below. If using a local account, the error does not occur. However, even with the error, the user is able to work just fine. Anyone seen the error below? I'm using Version 9.1.1.1

JKW

11/20/12 01:49:11 PM PST [INFO] [Workstation] Introscope Workstation Release 9.1.1.1 (Build 581768)
11/20/12 01:49:11 PM PST [INFO] [Workstation] Using Java VM version "Java HotSpot(TM) Client VM 1.6.0_31" from Sun Microsystems Inc.
11/20/12 01:49:11 PM PST [INFO] [Workstation] Using Introscope installation at: C:\Documents and Settings\mwjkw\Application Data\Wily\Introscope\product\workstation
11/20/12 01:49:11 PM PST [INFO] [Workstation] CA Wily Introscope(R) Version 9.1
11/20/12 01:49:11 PM PST [INFO] [Workstation] Copyright (c) 2012 CA. All Rights Reserved.
11/20/12 01:49:11 PM PST [INFO] [Workstation] Introscope(R) is a registered trademark of CA.
11/20/12 01:49:11 PM PST [INFO] [Workstation] Starting Introscope Workstation...
11/20/12 01:49:11 PM PST [INFO] [Workstation] Introscope Workstation started.
11/20/12 01:49:12 PM PST [INFO] [Workstation] PDF Force Line Break Policy is false
11/20/12 01:55:13 PM PST [INFO] [Workstation.Login] Successfully logged in user "JKW"
com.wily.introscope.spec.server.beans.session.IllegalActivityException: com.wily.introscope.permission.PermissionException: User JKW does not have sufficient permissions in domain Server Resource

at com.wily.apm.em.monitor.isengard.support.security.MonitorSecurityUtil.checkPermissions(MonitorSecurityUtil.java:23)

at com.wily.apm.em.monitor.isengard.support.SystemHealthStatusMonitorService.subscribeToHealthStatus(SystemHealthStatusMonitorService.java:139)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.wily.isengard.messageprimitives.MethodCallUtilities.callInterface(MethodCallUtilities.java:75)

at com.wily.isengard.messageprimitives.MethodCallUtilities.callInterface(MethodCallUtilities.java:29)

at com.wily.isengard.messageprimitives.service.MessageService.attemptMethodCall(MessageService.java:183)

at com.wily.isengard.messageprimitives.service.MessageService.handleMethodCallMessage(MessageService.java:135)

at com.wily.isengard.messageprimitives.service.MessageService.receiveMessage(MessageService.java:161)

at com.wily.isengard.postoffice.Mailbox.handleMessage(Mailbox.java:252)

at com.wily.isengard.postoffice.PostOffice.deliverInternal(PostOffice.java:501)

at com.wily.isengard.postoffice.PostOffice.access$1(PostOffice.java:447)

at com.wily.isengard.postoffice.PostOffice$DeliveryItem.run(PostOffice.java:786)

at com.wily.EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:728)

at java.lang.Thread.run(Thread.java:662)

Outcomes