<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic CKIP / LEAP on Secure Services Client 5.1.0.39 in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ckip-leap-on-secure-services-client-5-1-0-39/m-p/1104876#M73758</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am in the middle of converting over to a LWAPP infrastructure as well as converting over to using the Cisco Secure Services Client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because I have a very large number of IOS based AP's still in service that are running LEAP with CKIP, I have a need to simultaneously support both the LWAPP infrastructure and the old IOS based infrastructure at the same time (at least for now).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have the SSC working fine with my LWAPP WPA2/PEAP infrastructure, however I cannot get it to work on the old IOS LEAP/CKIP infrastructure.  There do not appear to be any CKIP options in the SSC, and I have tried all of the other options (including all of the TKIP options) and none seem to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So my question is, does the SSC v. 5.1.0.39 (the latest version) not support CKIP, or am I missing something.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any advice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Neil&lt;/P&gt;</description>
    <pubDate>Sat, 03 Jul 2021 23:20:37 GMT</pubDate>
    <dc:creator>neilhall</dc:creator>
    <dc:date>2021-07-03T23:20:37Z</dc:date>
    <item>
      <title>CKIP / LEAP on Secure Services Client 5.1.0.39</title>
      <link>https://community.cisco.com/t5/wireless/ckip-leap-on-secure-services-client-5-1-0-39/m-p/1104876#M73758</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am in the middle of converting over to a LWAPP infrastructure as well as converting over to using the Cisco Secure Services Client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because I have a very large number of IOS based AP's still in service that are running LEAP with CKIP, I have a need to simultaneously support both the LWAPP infrastructure and the old IOS based infrastructure at the same time (at least for now).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have the SSC working fine with my LWAPP WPA2/PEAP infrastructure, however I cannot get it to work on the old IOS LEAP/CKIP infrastructure.  There do not appear to be any CKIP options in the SSC, and I have tried all of the other options (including all of the TKIP options) and none seem to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So my question is, does the SSC v. 5.1.0.39 (the latest version) not support CKIP, or am I missing something.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any advice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Neil&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 23:20:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ckip-leap-on-secure-services-client-5-1-0-39/m-p/1104876#M73758</guid>
      <dc:creator>neilhall</dc:creator>
      <dc:date>2021-07-03T23:20:37Z</dc:date>
    </item>
    <item>
      <title>Re: CKIP / LEAP on Secure Services Client 5.1.0.39</title>
      <link>https://community.cisco.com/t5/wireless/ckip-leap-on-secure-services-client-5-1-0-39/m-p/1104877#M73759</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After getting no response here I opened up a TAC case with this exact same question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Per the TAC:  CKIP is not supported in the CSSC.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Aug 2008 17:26:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ckip-leap-on-secure-services-client-5-1-0-39/m-p/1104877#M73759</guid>
      <dc:creator>neilhall</dc:creator>
      <dc:date>2008-08-20T17:26:02Z</dc:date>
    </item>
  </channel>
</rss>

