Hi folks,
Sorry if it seems I am spamming the list but I just wanted to say thanks for
the help.
I have now updated to 6.0.1 and it is looking much better:-
The 'Null' and 'BlackHole' authentication module problems are gone.
We have our corporate logo back too!
Oh so many questions about 'customisation' and 'branding' though but the main
ones:-
How can I hide and/or replace the icon on the portal screens?
How can I change the colour schemes?
I was able to do most of this in 5.7 by modifying the main 'styles.css' file
but the new inuit.css system
renders this file uneditable. I can see the components/layers that produce this
file but how does
one 'compile' them to build the new CSS file after modifications.
I do have some technical portal issues that I cannot seem to work around no
matter what settings I use (some of the
individual bits worked in 5.7 though).
I have created a 'Choice' module as the only module in my ROOT.
The choice module has three sub-modules added:-
Choice 1 - An LDAP authentication module to register the Device - This works
and moves the device to the production network as expected.
Choice 2 - An E-Mail authentication module to register the device via an E-Mail
activation link - This sort of works.
The system reports a message - 'Couldn't register your device....' below which
it says it has registered it successfully and is
enabling access. - Surely they can't both be true!!!
The activation e-mail is indeed sent to the correct e-mail address along with
details of the local account that it has created for the user.
It will however not accept the activation link and comes up with the message
'Please use the device you are registering to validate
the e-mail link'. Which of course I am doing! (5.7 you could 'activate' it from
anywhere) - What could be wrong - any ideas?
The only thing I can see may be causing this is that I am doing role assignment
(and subsequent VLAN assignment) based on
the E-Mail account used - Using rules in the e-mail source definition. But I
was doing this in 5.7 and it was working beautifully.
We have 2 separate universities (Falmouth and Exeter) using the campus networks
and need to move them onto the correct subnets
whenever possible and this seemed to be a good way of doing it - Not all users
are potentially authenticable via LDAP!
Choice 3 - A 'chained' authentication module which consists of first an LDAP
authentication module followed by a message
module containing a link to the 'Device-Registration' portal.
The Authentication stage is working as expected and the
Device Registration stage is sort of working but it is
registering the device to 'default' and not the user that has just
authenticated.
It is kind of important that we have a record of who registers what devices but
at the moment all gaming devices would be 'owned'
by the user 'default'. Maybe I am misunderstanding the DR process but this is
how I interpreted it as working - First authenticate a
user then let them register a device.
Regards
Andrew
Andrew Torry
Network Infrastructure & Security Manager
Falmouth Exeter Plus
Penryn Campus, Penryn, Cornwall TR10 9FE
Direct Line: 01326 370760
Email: [email protected]<mailto:[email protected]>
Web: www.fxplus.ac.uk<http://www.fxplus.ac.uk/>
[Description: Description: Description:
cid:96145AF1-BADB-420E-99CB-36E729C912FD]
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
