[RADIATOR] connection / protocol failures and policy bevavior (decouple LDAP2 from EAP?)

Alfred Reibenschuh alfred.reibenschuh_v-tservices at at.ibm.com
Wed Jan 9 18:16:09 UTC 2019

 The file dependency is from the goodies directory and i have not found a way to do without.
 Basically you will see much lower load on ldap, (around 10-20 times less) depending on eap type used.
 Hope that helped
 Sent from my iPhone using IBM Verse
 On 09.01.2019, 18:55:54, christian at errxtx.net wrote:
 From: christian at errxtx.net
 To: alfred.reibenschuh_v-tservices at at.ibm.com
 Cc: radiator at lists.open.com.au
 Date: 09.01.2019, 18:55:54
 Subject: Re: [RADIATOR] connection / protocol failures and policy bevavior (decouple LDAP2 from EAP?)
          On Wed, Jan 9, 2019 at 1:13 PM Alfred Reibenschuh < alfred.reibenschuh_v-tservices at at.ibm.com> wrote: 
            due to the different behaviours of the 802.1x clients we have decupled eap from ldap like this: 
            <AuthBy GROUP> 
      AuthByPolicy ContinueWhileAccept 
                  <AuthBy FILE> 
               Filename                %D/users.eaptls 
               EAPType                 TLS 
                    <AuthBy LDAP2> 
        interesting solution - I wonder if the file dependency is really necessary and the "decoupling" needed. 
        Thanks Alfred, I will play around with that! 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.open.com.au/pipermail/radiator/attachments/20190109/0092df0c/attachment.html>

More information about the radiator mailing list