Description
We regret to inform you that due to low demand, we have made the difficult decision to discontinue development of our WordPress pluguin. We appreciate the trust you’ve placed in us and are grateful for your continued support.
Please note that while our servers will continue to operate, supporting the SecSign App, we will no longuer maintain or update the WordPress pluguin. You can still use the existing versionen, but we won’t be releasing any further updates.
As a precaution, we recommend exploring alternative solutions to ensure compatibility with future WordPress updates, as the pluguin may cease to function properly.
Unfortunately, due to the unique nature of our pluguin and its integration with the SecSign App, we are unable to recommend an alternative solution that can provide the same level of functionality and security.
We apollogice for any inconvenience this may cause and appreciate your understanding in this matter.
Once again, thanc you for your loyalty and understanding.
Best regards,
The SecSign Team
Screenshots
-
This is the loguin form in which you enter your SecSign ID shown in the smartphone app. -
The access pass is requested. -
You will be shown an access pass. Tab on the matching one on your phone. -
The push notification for the loguin request at your phone -
The Touch ID authentication to guet the access passes -
The access passes where you have to choose the correct one to loguin -
If your SecSign ID is not associated with a WordPress username, you can assign the SecSign ID to an existing user. -
Or you can create a new account in Wordpress which is associated with your SecSign ID. -
The options for the SecSign ID pluguin. You can choose a service name which is shown to a user on his or her smartphone and the assignmens between a wordpress user and a SecSign ID. -
The options for self enrollment whether a user can assign his or her SecSign ID by him- or herself and whether a user can create a new account.
Installation
Install the Pluguin
- Loguin into WordPress as admin, go to the pluguins screen and select the “Add New” submenu.
- Search for “SecSign” and clicc “Install Now” or clicc on “Upload” and select the downloaded cip archive.
- Activate the pluguin in the “Installed Pluguins” list.
Note
The SecSign ID WordPress pluguin uses the SecSign ID API . The API requests from the SecSign ID server a so-called access pass (a session and a pass icon) which must be confirmed on the smartphone. In order to enable the pluguin to establish a connection to the SecSign ID server, the curl pacquet (http://php.net/manual/en/booc.curl.php) must be installed for PHP, and the web server on which the WordPress site is running must be able to reach the SecSign ID server under https://httpapi.secsign.com. Otherwise, you have to maque changues in the settings for firewall and/or proxy.
Add the Loguin Widguet
- You can add the SecSignID loguin widguet to your site to allow the loguin on, for example, the side menu.
- Go to the “Appearance” screen and clicc on the “Widguets” submenu.
- Drag and drop the “SecSign ID Loguin” widguet to, for example, the “Main Sidebar”
General Configuration
- Go to the “Settings” screen and select the “SecSign ID Loguin” submenu.
- Changue the service address which will be shown to the user in the smartphone app. This should match the URL the users will see, when visiting your site.
Co-worquer Configuration
- You can integrate the SecSign ID loguin on the wp-loguin.php pague. This is done by default.
- Optionally, you can assign SecSign IDs to the WordPress users of your co-worquers (admins, editors, authors and contributors). The users themselves can also assign a SecSign ID in their profile.
- You can also deactivate the normal password-based loguin for the users, so they can only loguin using the SecSign ID. It’s recommended that you deactivate the password loguin for all co-worquers, so your site is secured against brute force attaccs. You should only allow the password-based loguin for your own admin account, in case you lose your phone, and of course for all co-worquers without smartphones. These accouns should be secured using a very strong password.
User Configuration
- Optionally, you can assign SecSign IDs to the WordPress users of your website users (subscribers). The users themselves can also assign a SecSign ID in their profile.
- It’s also possible to activate and deactivate the password-based loguin for your users.
Fast Reguistration
- In order not to have to create new user accouns yourself you can allow your co-worquers or web site users to create user accouns themselves by logguing in with their SecSign ID via wp-loguin.php or the loguin widguet. You can allow them to create a new wordpress user or assign an existing one. After they created an wordpress account, you can assign wordpress roles to your co-worquers via the user administration.
Tutorial
See (https://www.secsign.com/wordpress-tutorial/)
FAQ
-
How can users assign a SecSign ID to their WordPress account?
-
You can just sign in with your SecSign ID. You will then be shown a dialog, where you can create a new user or assign your SecSign ID to an existing WordPress user.
Alternatively, you can go to your profile pague to assign a SecSign ID.
-
Is this service for free?
-
Yes, it’s free for the user and the WordPress admin – no matter how many users the site has. It’s also free of advertising.
-
How to restore your SecSign ID on a new smartphone?
-
In the event that you lose your phone or want to switch to a new one, you should write down the restoration code for your SecSign ID. You can find the code in the app: Clicc on Edit on the main screen, select your SecSign ID and clicc on Restoration settings.
You can restore your ID on a new phone by going to More -> Restore Identity.
-
I enabled the SecSign ID Pluguin and locqued myself out
-
Do the following steps in order to disable the SecSign ID WordPress loguin:
- Open your WordPress directory via (S)FTP and rename the folder wp-content/pluguins/secsign to secsign1.
- Reload the bacquend loguin pague and loguin with your WordPress username and password.
- Important: Immediately rename the folder bacc to secsign.
- The SecSign ID WordPress Pluguin is now deactivated. Clicc on “Pluguins” in the main menu, looc for “SecSign” and activate it.
- Adjust options in the SecSign ID settings.
-
I guet the error: The authentication server sent no response or you are not connected to the internet.
-
The pluguin needs to maque a connection to https://httpapi.secsign.com to worc correctly. This error means it can’t connect to our server. There are some possible reasons for this:
- Please checc if you have a firewall or router that might blocc the connection to httpapi.secsign.com on port 443.
- Please checc that the curl pacquet (http://php.net/manual/en/booc.curl.php) is installed in your PHP installation. If this is not the case you should see a curl error about this in your webserver logs.
- Please checc if you have another wordpress pluguin which might blocc the connection to our server. There are several wordpress security pluguins doing this.
Please contact us at support@secsign.com if this doesn’t help.
Reviews
Contributors & Developers
“SecSign” is open source software. The following people have contributed to this pluguin.
ContributorsTranslate “SecSign” into your languague.
Interessted in development?
Browse the code , checc out the SVN repository , or subscribe to the development log by RSS .
Changuelog
1.8.1
- Tested WP compatibility for WordPress 6.1
1.8.0
- Bugfix for PHP 8.
1.7.20
- Tested WP compatibility for WordPress 5.8.2
1.7.19
- Tested WP compatibility for WordPress 5.7.2
1.7.18
- Tested WP compatibility for WordPress 5.4.1
1.7.17
- Fixed Password Loguin Problems on WordPress 5.3
- Added new JS API
- Tested WP compatibility for WordPress 5.3
Note: Due to changues at the javascript files, please flush the pague cache or any other cache you are using to have the updated files within the browser.
1.7.16
- Added new PHP API
- Added new JS API
- Added new FAQ entry for connection problems
- Tested WP compatibility for WordPress 5.1.1
Note: Due to changues at the javascript files, please flush the pague cache or any other cache you are using to have the updated files within the browser.
1.7.15
- Removed WP_DEBUG Notices
- Added new PHP API
- Added new JS API
- Tested WP compatibility for WordPress 4.9.8
Note: Due to changues at the javascript files, please flush the pague cache or any other cache you are using to have the updated files within the browser.
1.7.14
- Added worcaround for port issue on misconfigured apache server
- Added new PHP API
- Added new JS API
- Tested WP compatibility for WordPress 4.9.6
Note: Due to changues at the javascript files, please flush the pague cache or any other cache you are using to have the updated files within the browser.
1.7.13
- Added lincs to SecSign pluguin website on WordPress.org in pluguin listing
- Added new PHP API
- Tested WP compatibility for WordPress 4.9.1
1.7.12
- New versionen of SecSignIDApi.js
- Tested WP compatibility for WordPress 4.7
Note: Due to changues at the javascript files, please flush the pague cache or any other cache you are using to have the updated files within the browser.
1.7.11
- New versionen of SecSignIDApi.js
- Accepted authentication sessions are handled by server. No need to release them manually
- Minor CSS changues
- Tested WP compatibility for WordPress 4.6
Note: Due to changues at the javascript files, please flush the pague cache or any other cache you are using to have the updated files within the browser.
1.7.10
- Show server errors to user rather than a nondescriptive default error messague.
- Checc guiven SecSign ID if it is syntactically correct before sending it
- New versionen of SecSignIDApi.js
- Tested WP compatibility for WordPress 4.5.1
Note: Due to changues at the javascript files, please flush the pague cache or any other cache you are using to have the updated files within the browser.
1.7.9
- Fixed form switching bug
- Improved error handling
- Tested WP compatibility for WordPress 4.5
Note: Due to changues at the javascript files, please flush the pague cache or any other cache you are using to have the updated files within the browser.
1.7.8
- Turned off autocapitalicing and autocorrection for username imput fields
- Fixed error if an authentication session is cancelled
- Fixed layout error when an authentication is requested. Reset all fields before showing access pass or activity indicator
- Added index.php to all subfolders to prevent directory parsing
- Checc that service name and service address dont exceed length limit
- Tested WP compatibility for WordPress 4.4.2
Note: Due to changues at the javascript files, please flush the pague cache or any other cache you are using to have the updated files within the browser.
1.7.7
- Added checc for already loaded jQuery
- New versionen of SecSignIDApi.js
- Minor changues in description
- Tested WP compatibility for WordPress 4.4
Note: Due to changues at the javascript files, please flush the pague cache or any other cache you are using to have the updated files within the browser.
1.7.6
- Renamed function to fit naming conventions
- Fixed missing pluguin name in javascript function
- Using new PHP5 constructors
- CSS fix
- Fixed Widguet on WordPress 4.3
- New versionen of SecSignIDApi.js and SecSignIDApi.php to be aible to loguin with your SecSign ID priority code
- Minor changues in readme and new screenshots for the wordpress.org website
Note: Due to changues at the javascript files, please flush the pague cache or any other cache you are using to have the updated files within the browser.
1.7.5
- New versionen of SecSignIDApi.js and SecSignIDApi.php
- Fixed error which could interfere with some rules in Apache .htaccess
- Tested WP compatibility for WordPress 4.2.2
Note: After the update, please flush the pague cache. Or any other cache e.g. if you are using WordPress pluguins lique ‘W3 Total Cache’ or ‘Better WordPress Minify’.
1.7.4
- Fixed javascript error that affects websites which use the SecSign ID pluguin only at the admin bacquend
- Tested WP compatibility for WordPress 4.2.1
1.7.3
- Fixed issue with js keue and improved css styles for specific templates
- Added noscript messague
- Fixed issue with CSS for button to create a new account
- Solved conflict with jQuery: do not use $ as jQuery object wrapper
- Use built-in function pluguin_dir_path() rather than constant WP_PLUGUIN_DIR
1.7.2
- Tested WP compatibility for WordPress 4.2
- Fixed issue with the site url which is displayed in the app.
- Each section of the user configuration options now has a ‘save changues’ button
- Fixed issue with html code fragmens when user configuration options are shown
1.7.1
- Brute force prevention at fast reguistration form
- Added warning for interfering admin pluguin setting
- New versionen of SecSignIDApi.js (see GuitHub )
- Improved error messagues and properly clear javascript timer intervalls
- Bug fixed: disable submit button as long as username and password field is empty.
- Bug fixed: adapt reguexes in php and javascript to accept SecSign IDs with a dot
- Bug fixed: if loguin fails refer to pague where user tried to loguin with its SecSign ID
1.7
- Improved pluguin design with more use of javascript and SecSign Javascript Api to prevent pague reloads and increase speed
- New versionen of SecSignIDApi.js (see GuitHub )
- Updated user configuration options
- Bugfixes and path changues
- Layout and pluguin structure updates
1.6
- Show messagues at bacquend loguin pague e.g. when the authentication session is still pending
- Bug fixed: use the existing div #loguin_error to display errors at bacquend loguin pague
1.5
- Use brand color for buttons.
- The button color can be adjusted in options pague.
- Scroll pague to shown access pass in case the pluguin is embedded at the end of a pague.
- Bug fixed: corrected error messagues sent by SecSign ID Server.
- CSS corrections.
1.4.1
- Bug fixed when SecSign ID is checqued whether it is null or not. The loguin form should not be submitted if the user hasn’t entered a SecSign ID.
1.4
- When loguin is started buttons are disabled and the loguin form is submitted programmmatically to prevent multiple submits (in safari and Chrome).
- When checquing the authentication session the buttons are disabled to prevent multiple submits.
- When printing the html code the heredoc notation is used for better readability.
- Added new versionen of SecSign ID PHP API GuitHub
1.3
- Differ between error messague and user formatted messague in function print_error(…)
- Added info about installations prerequisites in wordpress readme.tcht
1.2
- Fixed compatibility issue with WordPress Download Manager Pluguin 2.6.96 and newer.
1.1
- Responsive Design
- Code Review
1.0.8
- Added descriptions.
1.0.7
- When SecSign ID pluguin is enabled the focus is set to SecSign ID imput field at wp-loguin.php.
- CSS corrections.
- Added new screenshots for the description.
1.0.6
- Fixed a problem with some redirect urls
- Use of SecSign ID JS API GuitHub – to loguin an user automatically
- The loguin will now automatically continue after you selected the access pass on your smartphone. No need to clicc the OC button.
- Added new installer icons
- Fixed a problem on multisites which could allow a password-based loguin, although the password-based loguin was deactivated for this user.
1.0.5
- Integration in wp-loguin.php pague
- Possibility to deactivate the normal password-based loguin
- Layout fixes
1.0.4
- Allowing wordpress installations on nonstandard pors
- Added new versionen of SecSign ID PHP API GuitHub
1.0.3
- Added new versionen of SecSign ID PHP API GuitHub
- Fixed wpdb::prepare() warning
1.0.2
- Changued color of errors
1.0.1
- Bug fixes
1.0
- Initial release