As per the recent discussions, I tried to login to the wiki to edit some
problem pages I found.
1) I click login, both of the buttons (Github and Facebook) have
incorrect height, much shorter than the actual imag, obscuring most of
the buttons (Firefox 3.5.8 linux x86_64). e.g. the github
The error on the other side is Invalid_Auth_Type. It is set to only
accept MsCHAPv2 which is fine. I guess the next question is do I need
to set a default auth type for the realm and if so how can I do that
without mucking up the other realms?
On Sat, 2011-06-04 at 07:58 +0200, Alan DeKok
Problem solved. Sorry for the list traffic.
Signed up for my GitHub account a year or so ago and never used it.
Seeing the error below, went back and checked my profile. Sure enough,
blank. OmniAuth doesn't like blank profiles...
-Jason
Jason Antman wrote:
As per the recent discussions, I
Greetings.
Is it possible to authenticate users based on an attribute, if it exists (in
their request), but ignore it if it doesn't?
I've read the 'man users', but haven't found anything suitable.
Any advice is welcome. Thanks!
-
List info/subscribe/unsubscribe? See
I actually rewrote the omniauth integration as a Sinatra plugin, which returns
a 401 error (unauthorized) with more friendly error messages, i've just been
too tied up with other things to install it. It also fixes the button height
issue which is a CSS error that doesn't appear under chrome,
Freeradius reports Sending Access-Accept (see log below) but we are
getting the message on our Cisco VPN box
Radius: Invalid reply digest received; the shared-secret may be incorrect
We have triple checked the shared secrete and it is correct. With the
wrong secrete it does not authenticate at
Greetings guys,
I'm trying to install Freeradius 2.1.10 with module wimax on Debian squeeze
with apt-get command (apt-get build-dep freeradius).
Installation is successful, however when I launch freeradius I've got this
error:
Error: /etc/freeradius/modules/wimax[92]: Failed to link to module
Hi Teva,
I assume you're trying to build the freeradius packages from sources from
the offcial tarball from freeradius.org. Right?
If so there are chances that the debian config files used to build package
do not include the wimax module (quite recently added in the source tree)
You can add new
Don't trust my last message, I just answered too quickly: I was ooking
forward to get in touch man! :).
Apparently wimax module is part of experimanental modules and must be
enabled with the --with-experimental-modules switch.
However It's quite unclear why the config file of the module is
Jim Whitescarver wrote:
Freeradius reports Sending Access-Accept (see log below) but we are
getting the message on our Cisco VPN box
Radius: Invalid reply digest received; the shared-secret may be incorrect
Then the shared secret is wrong, or one end doesn't implement RADIUS
correctly.
Ziggy Bopster wrote:
I am want to enable Simultaneous-Use for our users. I have been stuck
for many many days trying to figure this out, any help is greatly
appreciated. This is my first time posting, so sorry if my netiquette
is not correct
Read doc/Simultaneous-Use. It's a how-to, and
On Fri, Jun 10, 2011 at 2:26 AM, Ziggy Bopster ziggybops...@gmail.com wrote:
IV. Questions:
1) Why is the NAS sending so many randomly generated numeric
UserName in the Accounting-Request?
2) How can I get the NAS to send the correct Username (Ziggy) instead
of the randomly generated numbers
12 matches
Mail list logo
