包含:登录失败锁定、90天密码有效期、30分钟会话超时、 强制改密、登录审计日志、屏幕水印、企业背景图、 备案信息固定底部、favicon、登录页JS修复等全部改动
This commit is contained in:
+59
@@ -0,0 +1,59 @@
|
||||
MRBS provides an authentication type that allows the authentication of users
|
||||
against Wix websites. To install and configure this, you need to make changes
|
||||
on both the Wix and MRBS servers.
|
||||
|
||||
On the Wix site
|
||||
===============
|
||||
|
||||
1. Create a http-functions.js file in your Wix backend (see the Wix YouTube
|
||||
video at https://www.youtube.com/watch?v=4yCBplV3MPQ for how to do it) and copy
|
||||
and paste the contents of the file wix/web/http-functions.js into it. You will
|
||||
need to open the file with a suitable text editor such as Notepad++. If you
|
||||
already have a http-functions.js file you will need to merge the contents with
|
||||
your existing file.
|
||||
|
||||
2. Publish the file by clicking the "Publish" button.
|
||||
|
||||
3. In the Wix Secrets Manager (found under Developer Tools in your Wix
|
||||
dashboard) create a new secret called "MRBS_API_key". (You can choose your own
|
||||
name, but if so you will need to change the MRBS configuration - see below.)
|
||||
Generate an API key (search the web for "API key generator" or "GUID generator".
|
||||
Copy and paste this key into the secret and store it.
|
||||
|
||||
4. In your Wix dashboard, go to Contacts then Site Members. Under "Manage
|
||||
Badges" create a new badge called "MRBS Admin" and assign this badge to those
|
||||
members that should be admins. You can call the badge something else, in which
|
||||
case you should change the relevant MRBS config setting - see below.
|
||||
|
||||
[Using badges is not ideal for this purpose. The best solution would be to use
|
||||
Wix roles, but as of Jan 2022 there doesn't seem to be a way of getting the
|
||||
roles of a member given a memberId. Custom fields in members could be another
|
||||
solution, but there doesn't seem to be a way of stopping a member from editing
|
||||
their own custom field value in their profile. Therefore badges seem to be the
|
||||
only solution. Note though that badge titles don't have to be unique, so care
|
||||
should be taken. It might be better to use badge ids, but there doesn't seem
|
||||
to be a way for a Wix administrator to discover the id of a badge from the
|
||||
dashboard.]
|
||||
|
||||
|
||||
On the MRBS site
|
||||
================
|
||||
|
||||
Set the following configuration variables in your config.inc.php file:
|
||||
|
||||
$auth['type'] = "wix";
|
||||
|
||||
// The URL of your WIX site
|
||||
$auth['wix']['site_url'] = "https://example.com/";
|
||||
|
||||
// The API key that you generated and saved in your Wix secrets manager.
|
||||
$auth['wix']['mrbs_api_key'] = "";
|
||||
|
||||
// The name of the secret in your Wix secrets manager
|
||||
$auth['wix']['mrbs_api_key_secret_name'] = "MRBS_API_key";
|
||||
|
||||
// The name (title) of the badge that determines whether a member is an
|
||||
// MRBS admin. Note that badge names are case-sensitive. You can also
|
||||
// configure admins in the config file by using
|
||||
// $auth['admin'][] = "someone@example.com";
|
||||
$auth['wix']['admin_badge'] = "MRBS Admin";
|
||||
Reference in New Issue
Block a user