I am attempting to setup a new RADIUS server in our environment and move from FreeRADIUS 1.0.1 to FreeRADIUS 3.0+ (available in the SLES 12 repos) … however, I cannot find the LDAP module for FreeRADIUS after installation within the /etc/raddb/mods-available/ directory.
Is there a different way that needs to be handled now? The README in /etc/raddb/ seems to think it should be there.
Hi
Yup, looks like it’s missing. I checked the src rpm of the SLE 12 SDK
and it shows it present, but for what ever reason not in the pool…
Let me ping my SUSE contacts.
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.36-38-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
On 17/02/2015 19:34, boblmartens wrote:
[color=blue]
I am attempting to setup a new RADIUS server in our environment and move
from FreeRADIUS 1.0.1 to FreeRADIUS 3.0+ (available in the SLES 12
repos) … however, I cannot find the LDAP module for FreeRADIUS after
installation within the /etc/raddb/mods-available/ directory.
Is there a different way that needs to be handled now? The README in
/etc/raddb/ seems to think it should be there.[/color]
In looking into this I’ve also found that both krb5 and perl modules for
FreeRADIUS are also missing from mods-available (as is abfab_psk_sql but
I think that was added after 3.0.3). I’ve reported these omissions to SUSE.
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
As an aside, I would love to see some machinery for community members without support to be able to file and then track bug reports again SLE. Our current license has no SRs attached to it, but we try our best to report any “rough edges” we find and it would be nice to have more insight and access when we file these than the public bug reporting tool with no insight at all.
Just something to file away for the future. Thanks!
On 18/02/2015 13:34, boblmartens wrote:
[color=blue]
Thanks to both of you!
As an aside, I would love to see some machinery for community members
without support to be able to file and then track bug reports again SLE.
Our current license has no SRs attached to it, but we try our best to
report any “rough edges” we find and it would be nice to have more
insight and access when we file these than the public bug reporting tool
with no insight at all.
Just something to file away for the future. Thanks![/color]
It sounds like you’ve already found https://www.suse.com/support/report-a-bug/ where you can report a bug
without opening a Service Request but not receive any feedback so you’re
looking for something in between that and SRs? If so, I can’t see that
changing as I don’t see how SUSE would benefit from such a scheme.
There already exists a mechanism where SRs can be refund if an issue is
found to be a defect which hasn’t been publicly documented so I think
that’s your middle ground except you have to pay upfront.
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
[QUOTE=smflood;26435]
It sounds like you’ve already found https://www.suse.com/support/report-a-bug/ where you can report a bug
without opening a Service Request but not receive any feedback so you’re
looking for something in between that and SRs? If so, I can’t see that
changing as I don’t see how SUSE would benefit from such a scheme.
There already exists a mechanism where SRs can be refund if an issue is
found to be a defect which hasn’t been publicly documented so I think
that’s your middle ground except you have to pay upfront.
HTH.
Simon
SUSE Knowledge Partner[/QUOTE]
I think the value would be in those with licenses, but not SRs, being more willing to supply bug reports because they’d be able to see a little of what is going on with that bug report instead of firing-and-forgetting. More bug reports can help equal a higher-quality product which would make it a better sell to those who would need SRs.
That’s just from my (biased) point-of-view. Again, thanks for the help.
Back to the task at hand: any word on when/if we can expect an update?[/color]
If: yes, when: soon.
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------[/QUOTE]
Thank you greatly for your help and assistance.
As an aside, I would love to see some machinery for community members without support to be able to file and then track bug reports again SLE. Our current license has no SRs attached to it, but we try our best to report any “rough edges” we find and it would be nice to have more insight and access when we file these than the public bug reporting tool with no insight at all.
Just something to file away for the future. Thanks![/QUOTE]
Do you know if anyone has opened an SR with this request?