Recently I found that multiple accounts are being created in my Drupal 6.22 website by someone from a particular IP. Is someone aware of any modules to limit the user to create only one account per ip?
Thanks.
You have to use rules module for this. there is no direct module. Visit this link click here
Related
Is it possible allow a visitor to see only a post?
I think it would be safer if it is restricted by IP instead by cookies.
For instance the plugin WP POST RATINGS of Lester Chan has the option to allow 1 voting by IP.
If you’re not requiring a login, Cooke’s or local storage are you’re only viable solution.
IP checks are flawed in that any number of users on a local network will make requests from the same public IP address.
I understand your concern but most users are not incentivized or knowledgeable enough to understand that clearing their cookies would potentially allow a second “vote”.
So unless you go to a full Auth system you’re better off with cookies.
Hide another pages for visitor. You can use "Anonymous Restricted Content" plugin for hide page for not logged in users.
I want to be able to export a list of members from Netsuite and store their email domains in the backend of Wordpress. I am setting up a separate member portal through wufoo/Wordpress so that when a potential new member goes to register through our Wordpress site, the site automatically searches through the email addresses on file and work out whether that person is eligible to sign up for membership.
Hope this make sense?
Is this possible?
Thanks in advance
Enable REST in Wordpress Jetpack and call the rest API using nlapiRequestURL.
We have a customer with an unusual request for the security of a subset of a DotNetNuke / Evoq website.
This is a special set of pages that should only be accessed by a large group of a company's employees to make preferred-discount purchases.
Rather than trying to maintain a set of thousands of user accounts, having the employees register to gain access passwords, they just want to have the employee get to a welcome page, provide their email address (which will be confirmed as from that company's domain) and then be sent a link or a link and temporary rotating passcode that grants access to that set of pages for just the duration of their session once they visit the link.
I've searched for any type of 3rd party module to accomplish this with no luck.
It has also been suggested this might be accomplished through some type of URL-masking process, which I suppose might even be done by a proxy outside of DNN.
Has anyone provided a similar type of security solution before, either within DotNetNuke or through a proxy?
Any one know about how to change default error pages in PingFederate 6.10 during sso login. for example, in PF after no of unsuccessfull attempts exceeded user face error page from PF.
my question is how to change default ping federate sso user facing pages to refer external web pages? (i noticed too many inbuilt error pages are in Ping Federate)
Thanks in Advance....
Check the PF 6.10 Admin Guide to start -
https://documentation.pingidentity.com/display/PF610/Customizing+User-Facing+Screens#CustomizingUser-FacingScreens-1163105
You can modify these to add redirects to your own pages or customize these for your own message/look & feel.
If you have more questions on this, please post a new question.
My users access Drupal through SSO and everytime the server authorizes them, it returns a set of permissions (groups/roles), according to which I need to dynamically set the User's forum permissions.
So for example if a User logs in and the SSO says that he has enrolled in a course, I need to give him specific permissions for that course's forum.
Obviously I need a custom module for that, but it's a little hard to start.
I'm thinking of using the ACL module's API, but I can find any documentation or tutorial online. Is there any?
Is there a better way to get around this?
I'd appreciate any help :)
(note: I know there are modules with GUI that have similar functionality but I need to do it programmatically)
We just put something exactly like this into place - we used the Rules module (with the User logged in trigger), checking the LDAP groups that the user is enrolled in, and assigned the role accordingly.
Check out Forum Access. It can restrict users based on their roles.
You could have your roles be something like "CSC221 Student". If a user has this role, they will be able to access the CSC221 forum.
Create a hook_user function ( see http://api.drupal.org/api/function/hook_user ) in your module.
Then using http://drupal.org/project/permissions_api set the appropriate permissions on the user.