UFP Identity is the only dynamic security platform created for e-commerce sites, design agencies and developers that simplifies login authentication.
If there is a token, we support it. UFP Identity supports a wide variety of secure tokens enabling faster, more streamlined access to your websites all the while protecting user accounts from being compromised and preventing spam enrollments to your website.
UFP Identity set out to solve a huge technical challenge: To protect (I mean really, really make private!) online user’s personal info, make the process to access any number of websites at once really easy, and stop bad guys from hacking your stuff.
Our technology platform includes:
- Strongest level of password authentication and encryption!
- Spam protection preventing unwanted user account creation
- Account-compromise protection
- Threat level adjustment to heighten login protection for your users
- Seamless token integration (password, Yubico, OTP, various OATH tokens, one-time codes to phone/email/irc)
- Quicker logins for your users. By the way we’re building a mobile app for that.
- Universal password support for websites that use UFP Identity. This means login credentials can work on multiple websites.
- Real-time monitoring of every login ensures your users are your users
- Reporting tool for website administrators details every login transaction and outcome (coming soon!)
- Multiple tokens to single account
- Multiple accounts to single account
Certificate Signing Request
The Certificate Signing Request requires a private/public key
pair and the private key is encrypted with a secret key. In order to
create a good secret key the plugin attempts to get good random data
from /dev/urandom. If this fails, the plugin makes an attempt to
securely retrieve random data from https://www.random.org
Activating this plugin by installing the certificate will upload
information about your users to our servers. We only enroll the
username, email and hashed password over a private SSL connection
using 2048 bit keys. We will never use any information about your
users for any purpose other than authentication and verification. We
will never use the email for any purpose other than resetting
credentials or authentication. We will never sell or give up any of
the information about your users.
We send telemetry data to our servers over an SSL connection with 2048 bit keys. This telemetry data only contains data that we
would otherwise get with a successful install of the UFP Identity plugin. The telemetry can be turned off by adding an option
‘identity_telemetry_enabled’ => ‘no’.
We make a call to http://freegeoip.net/json/ to get location information for the Certificate Signing Request. This
is to help pre-populate the required fields and minimize the amount of work you need to do. We only do this once, upon install.
The WordPress UFP Identity plugin requires OpenSSL.
- Just activating the plugin will not protect your site with UFP Identity. If you need help please email us at firstname.lastname@example.org
- As admin, navigate to Plugins/Add New, Search Plugins for ‚UFP Identity‘
- Click the ‚Install Now‘ link in the search results for ‚UFP Identity‘ and confirm the installation
- After a successful installation, click ‚Activate Plugin‘
- Navigate to Settings/Identity
- Create a Certificate Signing Request following the instructions, if successful the CSR will be mailed to email@example.com
- Upon receiving a certificate, navigate to Settings/Identity and install the certificate. This will cause existing users to be enrolled with UFP Identity
- After enrolling existing users, the plugin will be fully initialized and handling logins for your site.
Für dieses Plugin gibt es keine Rezensionen.
Mitwirkende & Entwickler
„UFP Identity“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:Mitwirkende
- Initial version
- changed readme to reflect install from wordpress.org
- identity enabled for new users, even while enrolling and editing is disabled
- disable delete user if editing disabled. n.b. no way to indicate why delete was stopped
- more detailed status on Settings/Identity
- if openssl_random_pseudo_bytes doesn’t exist, try uniqid
- telemetry on activate, deactivate, uninstall
- fix check status and call it if editing disabled and nothing scheduled
- Pulled out loading up library so that it can be used in places that don’t require the provider loaded.
- handle reset properly
- static method call generates E_STRICT warning
- check to make sure certificate file uploaded is really a certificate file
- additional text changes
- removed un-necessary label
- migrate to strong, cohesive naming strategy
- fix missing locality description; add in Company/Organization header
- removing old drupal links; expecting wordpress links
- remove need for output_buffering
- remove cURL dependencies
- handle both cases users_can_register = TRUE/FALSE
- simplify enrollment check timing
- update instructios for CSR creation
- remove documented requirement for cURL
- describe location functionality
- formatting and some additional explanatory text
- prefill as much as we can for CSR
- nothing to remove with interim_login
- admin notice that identity is not installed
- clean up unused certificate files
- copy key to certificate file if dealing with PHP_VERSION < 5.3.3
- must specify mode to fopen
- if we don’t handle the login page return an empty error
- only prevent updates/edits when editing is disabled
- indicate status more simply and clearly
- really simplify checking enroll status
- tested with 4.0
- woocommerce integration
- consistent usage of true vs. TRUE
- reduction in irrelevant error_log’ing
- don’t override color in username input
- handle profile update with errors and potential blank user
- handle whether token is resettable (forgot password)
- override pluggable wp_check_password