Hello team   Is it possible to push a CA cert (Root / Sub) to an AP?   What we're trying to achieve is AP 802.1x authentication with ISE who's certs have been issued by a private PKI issuing CA.  Since the AP attempts to validate the ISE device cert during the mutual authn phase prior to 802.1x EAP/EAP-TLS transactions, the AP does not trust the cert presented by ISE and prevents the AP from initiating dot1x AuthN   one approach we're considering is to push a CA cert down to the AP.   ISE Live Logs: Event 5411 Supplicant stopped responding to ISE Failure Reason 12931 Supplicant stopped responding to ISE after sending it the first EAP-TLS message Resolution Verify that supplicant is configured properly to conduct a full EAP conversation with ISE. Verify that NAS is configured properly to transfer EAP messages to/from supplicant. Verify that supplicant or NAS does not have a short timeout for EAP conversation.  Check the network that connects the Network Access Server to ISE. Root cause Supplicant stopped responding to ISE after sending it the first EAP-TLS message   thanks for any guidance or recommendations. Regan ... View more

Hello Team.   we have a requirement to build policy around the user identity; while also user machine certificates to authenticate the computer.   is it possible to build an authorization policy that combines the results for both EAP-TLS (cert for machine) and PEAP-MSCHAPv2 (User credentials)?   the goal is to provide network access based on the combined machine and user authentication results.   thanks ... View more

hello folks, I would like to get some guidance on the below issue i experienced; i was able to find a "temporary" solution / workaround however i'd like to understand how to address correctly. My Environment: Maven: apache-maven-3.5.0 Apache: apache-tomcat-7.0.78 Java: JDK 1.8 Context Service: SDK 2.0.1 i'm using Maven and apache plugin to build / deploy my servlet and context service resources / libs / dependencies to the web service webapp directory. however, when attempting to initialize and connect both client ( ContextServiceClient) and management ( ManagementConnector) instances to the Context Service i received the below error (First / Second). it wasn't until i copied the required resources "Manually" to the required location did the issues resolve. i had to work thru two errors to resolve the issue. the project is functioning as expected, however, i'm just looking to understand if this typical or, is there a better way to manage this? what i find odd is that the plugin and connector.property resources are located OUTSIDE the servlet app directory and located with the Apache Bin directory. First Error: Cause: Exception occurred while Loading the configurations java.io.FileNotFoundException: /Users/regandediana/Development/Tomcat/apache-tomcat-7.0.78/bin/./connector.property (No such file or directory) Resolution: manually copy "Connector.Property" file to the "Apache_Home/bin" directory. Second Error: Cause: Exception occurred while Loading the configurations java.io.IOException: Cannot find the specified path: /Users/regandediana/Development/Tomcat/apache-tomcat-7.0.78/bin/plugin Resolution: manually copy "Plugin" director containing "context-service-sdk-extension-2.0.1.jar" file to "Apache_Home/bin" directory. any guidance, best practices, or direction would be greatly appreciated. Regan ... View more

Hello All. i'm attempting to update a pod customerId UUID value. in the below example, i get the interesting customer and pod objects, i attempt to update the pod object with the UUID of the customer object, then get the pod object from context service. however, my pod is not updating with customerId UUID. Code: // get customer Customer customer = contextServiceClient.get(Customer. class , "e72a2190-593b-11e7-844a-4d1470731c75" ); System. out .println( "Customer: " + customer.getLogString()); // get pod Pod pod = contextServiceClient.get(Pod. class , "f38ff160-5942-11e7-b26d-47831111becf" ); System. out .println( "Pod: " + pod.getLogString()); /// update pod CustomerId value pod.setCustomerId(customer.getCustomerId()); // get pod pod = contextServiceClient.get(Pod. class , "f38ff160-5942-11e7-b26d-47831111becf" ); System. out .println( "Pod: " + pod.getLogString()); Output: * as you can see the customerId: is null in both console outputs. Before Update: Pod: POD key: f38ff160-5942-11e7-b26d-47831111becf, refUrl: /context/pod/v1/id/f38ff160-5942-11e7-b26d-47831111becf, customerId: null, state: active, mediaType: null, requestId: null, contributors: [com.cisco.thunderhead.Contributor@3a574a3b[contributorType=machine,username=6e6f651b-1631-4616-9a5e-7a5ddde69f20,id=<null>]], fieldsets: [cisco.base.pod], workgroups: {production=[{keyId= https://encryption-a.wbx2.com/encryption/api/v1/keys/f391fcdb-3e91-4230-8802-151c089f6659 , encryptedSCR=***}, {keyId= https://encryption-a.wbx2.com/encryption/api/v1/keys/f391fcdb-3e91-4230-8802-151c089f6659 , encryptedSCR=***}]}, tags: [], dataElements: [dataElement key and value: *****:*****, type: string, dataElement key and value: *****:*****, type: string, dataElement key and value: *****:*****, type: string, dataElement key and value: *****:*****, type: string, dataElement key and value: *****:*****, type: string], created: 2017-06-25T01:09:34.710Z, lastUpdated: 2017-06-25T01:09:34.710Z, dataEnc: *****, piiDataEnc: ***** After Update Pod: POD key: f38ff160-5942-11e7-b26d-47831111becf, refUrl: /context/pod/v1/id/f38ff160-5942-11e7-b26d-47831111becf, customerId: null, state: active, mediaType: null, requestId: null, contributors: [com.cisco.thunderhead.Contributor@5418893c[contributorType=machine,username=6e6f651b-1631-4616-9a5e-7a5ddde69f20,id=<null>]], fieldsets: [cisco.base.pod], workgroups: {production=[{keyId= https://encryption-a.wbx2.com/encryption/api/v1/keys/f391fcdb-3e91-4230-8802-151c089f6659 , encryptedSCR=***}, {keyId= https://encryption-a.wbx2.com/encryption/api/v1/keys/f391fcdb-3e91-4230-8802-151c089f6659 , encryptedSCR=***}]}, tags: [], dataElements: [dataElement key and value: *****:*****, type: string, dataElement key and value: *****:*****, type: string, dataElement key and value: *****:*****, type: string, dataElement key and value: *****:*****, type: string, dataElement key and value: *****:*****, type: string], created: 2017-06-25T01:09:34.710Z, lastUpdated: 2017-06-25T01:09:34.710Z, dataEnc: *****, piiDataEnc: ***** any guidance or suggestions welcome! Regan ... View more