Jump to content

Extension talk:SemanticAccessControl

Add topic
From mediawiki.org
Latest comment: 10 years ago by Kghbln in topic Google Code Shutting Down


Installation

[edit]

"Finally, upload pages under 'pages' folder and 'groups' folder to your site." < This needs clarification, please. Simply uploading these files to the /mw/ root or /extensions/ has no effect. Adam Edgington 22:50, 23 January 2012 (UTC)Reply

Update that section. Please modify it directly to make it clear if you still think it is unclear. Jasonzhang 23:13, 23 January 2012 (UTC)Reply
Jason, for future revisions, you could look into importing/exporting these pages from MediaWiki XML dumps to make it easier. Just a thought. Mtyeh411 (talk) 16:49, 22 June 2012 (UTC)Reply
Could you provide step by step instruction on how to add the pages manually? Or provide reference on how to use the wikibot? ptheys 23:45, 15 July 2012 (UTC)Reply
Please download wikibot.pl and try wikibot.pl --help. The help gives out complete information for how to use it.
Adding all the page manually is painful process. For each page, create the page with the filename as title, paste file content as page content and click save.
-jason Jasonzhang (talk) 22:45, 17 July 2012 (UTC)Reply
Hello,
I am quite new to programming and SMW, and I am experiencing difficulties with installing this extension manually. I could not login to view the demo, since I can't create an account on http://demo.flexdms.com.
As you suggested, I created pages for all the properties (with 'create property'), forms, templates and categories (also with create form/template/category), since I found no possibility for a function in SMW 'create a page' under special pages. Afterwards I manually edited these pages with the appropriate content. These steps were successful.
The problem I have, is, should I use 'create category' to create the pages 'Project ACL' and 'Project User Group'? How should they be added?
I would appreciate any help. Thank you very much in advance.
Kind regards 87.78.131.156 13:07, 24 February 2013 (UTC)Reply
For demo, you do not need to create User account. Just use provided user account. The Main_Page has the test account and password.
I updated the distribution. Right now you can use Special:Import to import all the pages. This makes life much easier. Check updated documentation. Jasonzhang (talk) 12:46, 25 February 2013 (UTC)Reply
Thank you for your very kind support. Freckle (talk) 08:09, 27 February 2013 (UTC)Reply

6 extensions - really essentiell? And is there an example page?

[edit]

Why I need 6 extensions, that I can use accesscontrol. Is it really essentiell?

Is there an example page, for testing this extension? Speedtook 09:49, 31 January 2012 (UTC)Reply

you could use the "semantic mediawiki bundle" which, I believe, contains the 6 extensions (but you need to activate some like the Semantic Internal Object one) Pierro78 15:57, 31 January 2012 (UTC)Reply
All six extensions are needed. As Pierro78 pointed out, you can use semantic mediawiki bundle plus this extension. Set up your own demonstration following the "Demonstration" section in the document. Jasonzhang 18:42, 31 January 2012 (UTC)Reply
Hello,
already we installed Semantic Mediawiki and Semantic Forms, also BlueSpice and LDAP Authentication. And we do not want install a lot of extensions, because if we must update our wiki, it will be more complicated. The extensions have to work together.
I do not know if SemanticAccessControl this extension is which I need.
We tried it with ImprovedAccessControl, but the problem is, this extension does not work in a template.
So it would be good, if I could test it before I have installed it, because else I must delete it again.
Thank you for your fast answers!
Kind regards Speedtook 13:06, 1 February 2012 (UTC)Reply
Some things have to be accepted the way they are. However, these extensions are easy going on upgrade. Cheers [[kgh]] 18:45, 1 February 2012 (UTC)Reply
I have a similar issue that all those extension may cause conflicts with my configuration.
In particular HeaderTabs I can't use because of the multiple extensions that conflict with it. Legaulph (talk) 17:47, 8 April 2015 (UTC)Reply

Sreenshots

[edit]

I don´t know if I understand the function of this extension. Can you upload any sreenshots, how a user works with this accesscontrol? Many thanks! 80.149.179.2 13:29, 9 February 2012 (UTC)Reply

sorry, no screenshot. Please download and try yourself out. Most likely, you only need to embed acl statement in template. There is no need for any GUI except defining user group from time to time. Jasonzhang 17:57, 9 February 2012 (UTC)Reply
It is possible with a form, right?
How such a form could look? Checkboxes with the groups? And what for permissions the users are able to choose? 80.149.179.2 09:10, 10 February 2012 (UTC)Reply
For example like that image? Would it work so?
Mediawikitester 12:15, 10 February 2012 (UTC)Reply

Configuration

[edit]

The instruction on the Page is

  • Configure default site access control rule. Edit UserGroup:SiteACL
  • Configure the default policy for user in one group. Edit UserGroup:GroupACL
  • Add any user who design the site. Edit UserGroup:Developers

When I open these pages i get empty pages. What should I add there? 129.27.219.242 14:02, 10 February 2012 (UTC)Reply

BTW Nice idea doing this semantically! 129.27.219.242 14:04, 10 February 2012 (UTC)Reply

How do I use the parser functions?

[edit]

For example: {{#allgroups}} or {{#allusers}} → didn´t work 80.149.179.2 16:24, 20 February 2012 (UTC)Reply

try this: {{#allgroups:0}} or {{#allusers:0}}. I guess you have to supply the : for the MediaWiki to recognize it is parser function. Jasonzhang (talk) 18:25, 20 February 2012 (UTC)Reply
{{#allgroups:0}} or {{#allusers:0}} didn´t work... 80.149.179.2 11:54, 1 March 2012 (UTC)Reply

namespace

[edit]

Hello, can I use this extension for pages in all namespaces? Or have to be the pages in namespace "ACL" ? Thanks Mediawikitester (talk) 14:24, 6 March 2012 (UTC)Reply

Sorry, I do not understand your question. Can you elaborate it a little more?
If you mean "is ACL namespace rquired", yes, it is required.
-jason 154.5.162.254 19:33, 6 March 2012 (UTC)Reply
Okay I try it in an example:
I have an existing page (Help:Administration) and I want to set access control...
Is that possible? Or I have to rename the page into: "ALC:Administration"? Mediawikitester (talk) 09:41, 20 March 2012 (UTC)Reply
Edit SemanticAccessControl.php, add NS_HELP to $ACL_CONTENT_Namespaces. Basically, you want SemanticAccessControl treats pages in help namespace as regular content page for user.
After this, you can apply access control rule in a mechanims provided by SemanticAccessControl Jasonzhang (talk) 17:46, 20 March 2012 (UTC)Reply

Pages, Templates, Forms, Categories for SemanticAccessControl

[edit]

Hi,

we have installed the rquired extensions. But we have no pages, templates, forms,... from this extensions (Pages like "Form:ACL_UserGroup" do not exist). Is it possible to export/import the pages from Google SemanticAccessControl Project Page?

Best regards! 80.149.179.2 07:06, 3 April 2012 (UTC)Reply

The pages(wiki text format) are inside of the distribution. You can use wikibot.pl in google project page to BATCH UPLOAD them to your wiki site. Jasonzhang (talk) 19:30, 3 April 2012 (UTC)Reply

Extension doesn´t work

[edit]

Hi, the extension doesn´t work. I saved a page with this code:

{{ACL Page User Permission
|User=Mediawikitester
|Permission=read, write, grant
|Grant=Grant}}

But all users can read and write :-( Mediawikitester (talk) 09:27, 3 April 2012 (UTC)Reply

and also anonymous users have access.
What could be my mistake? Mediawikitester (talk) 14:00, 3 April 2012 (UTC)Reply
You need EXPLICITLY deny access for ALL other users.
You can add statment like this
{{ACL Page Group Permission
|UserGroup=All Users
|Permission=write, read, grant
|Grant=Reject
}}
or Configure UserGroup:SiteACL. Jasonzhang (talk) 19:35, 3 April 2012 (UTC)Reply
Hi,
how do I set permissions for specific users?
For example:
I want to create a page, that only I have access.
Other users and anonymous should not able to read or write.
I tought that works with:
{{ACL Page User Permission
|User=Mediawikitester
|Permission=read, write, grant
|Grant=Grant}}
But after saving that page, still all can read and write :-( Mediawikitester (talk) 20:31, 4 April 2012 (UTC)Reply
Please read the documentation and my reply! First, check your installation and make sure Semantic Internal Object extensions works. If SIO does not work, this extension does not work, either. Second, please read my reply before. You have to explicitly deny access for ALL other users. Did you do it? Moreover, login may be required for all users. I did not test this user for anonymous user. In my test, login is required at my installation. Jasonzhang (talk) 17:28, 5 April 2012 (UTC)Reply
I feel like I must be missing something about this extension is supposed to work. I have installed it and all its requirements including SIO and they show up under Special:Version in my SMW instance. However, the only way I am able to get ACLs to work is by embedding the ACLs directly in the page, or via template.
I tried initially to block all access to the site following the example in the Development_notes.txt, I have set my SiteACL to:
{{ACL UserGroup |Users=All Users }} {{ACL UserGroup Permission |Permissions=write,grant,read |Grant=Reject }}
But still all logged in and anonymous users are able to view Main_Page, and any other page which does not have ACLs to deny access in the actual page content. The same applies to the GroupACL (also set to deny everything), and I have even tried to use Page ACLs (defined using the permissions menu) but they don't seem to work either.
Is there something I am missing about how this extension is supposed to work? Is it required to defined ACL properties on every page or something?
I am using mediawiki 1.22.1 and SMW 1.9.0.1. Any tips you can give would be appreciated 59.167.198.77 04:48, 29 January 2014 (UTC)Reply
add this to you template
{{ACL Page Group Permission |UserGroup=All Users |Permission=write, read, grant |Grant=Reject }}
Please note: owner always has every right.
Second, test to make sure SIO really work. I have many trouble with SIO. Sometime SIO just does not work even it is installer properly.
Live demo site is available right now. Check it too Jasonzhang (talk) 21:54, 29 January 2014 (UTC)Reply
I realise I can add a block all ACL to my page templates, but what about pages that don't use templates? From what I can understand from the documentation, the SiteACL should control access to all content pages even if they don't have ACLs in them. Is that assumption incorrect? Does the SiteACL only come into affect when other ACLs are evaluated first?
I have looked at the demo site but it's SiteACL is blank and the GroupACL is the default value. It would be very helpful if you could update it so there is an example of how to set these so they work.
I tested SIO with a dummy page using the set_internal function and it seems to be working fine.
Thanks again for your help. 59.167.198.77 23:56, 29 January 2014 (UTC)Reply
It seems that the 'All Users' does not work for SiteACL. This is a bug. As a workaround, you can set up site permission in LocalSettings.php following MediaWiki instruction. This extension will fall back into MediaWiki if no explicit deny or grant access is specified. Jasonzhang (talk) 17:00, 30 January 2014 (UTC)Reply
I am unable to get the SiteACL to work in any way, even by specifying UserGroups or individual users. The Development_notes.txt in the google code repository says the SiteACL applies to all users implicitly and the Users field is ignored in the SiteACL (line 35-36). Has the Semantic Access Control extension (or at least the SiteACL/GroupACL functionality) been verified to work with the latest versions of MW/SMW? Could this be a bug with the most recent versions? 59.167.198.77 01:04, 31 January 2014 (UTC)Reply
I verified in my demo site. SiteACL does not work. This is a bug in code. Again, SiteACL can be replaced with Wiki itself permission in LocalSettings.php. I did not verify GroupACL. Jasonzhang (talk) 20:45, 1 February 2014 (UTC)Reply
Is there an existing webside, which use this extension? It would be very helpful, if I had an example.
I need the information, what for forms, templates and UserGroups,... I have to create, that the extension works. Mediawikitester (talk) 07:37, 5 April 2012 (UTC)Reply
Sorry, No existing website. I do not have a public server at my dispose. Jasonzhang (talk) 17:30, 5 April 2012 (UTC)Reply
demo site is available right now Jasonzhang (talk) 21:55, 29 January 2014 (UTC)Reply
We installed the extension and it works perfect :) < /br>
Thank you! Mediawikitester (talk) 12:16, 14 March 2014 (UTC)Reply

How do I set permissions?

[edit]

How do I set permissions? With "edit with form" or with "Permission"-tab? 80.149.179.2 14:12, 3 April 2012 (UTC)Reply

Most likely, you want to embed permision syntax in template page. Please see the Usage sectionin documnetation Jasonzhang (talk) 19:27, 3 April 2012 (UTC)Reply

Deletion permission tab & ACL namespace

[edit]

Hi, we use access control only with a form and templates.
We don´t need the "permission" tab and the ACL namespace.
Is it possible to delete this tab and this namespace?
How can I delete these and does the Extension still work after that? 80.149.179.2 08:03, 26 April 2012 (UTC)Reply

To remove the permission tab, comment out line with 'PermissionTab' in the SemanticAccessControl.php.
Please keep the ACL namespace, it is not used if permission tab is removed. However, it is inside of the code. So it could break code if ACL namespace is removed.
It seems you get this extension worked.
By the way, I'd like to hear some your comment on this extension such as installatio, configuration and features.
thanks Jasonzhang (talk) 15:34, 26 April 2012 (UTC)Reply

Bugs

[edit]
: is namespace separator. You have to specify each protected namespace in $ACL_CONTENT_Namespaces. Please refer to configuration section Jasonzhang (talk) 16:48, 16 October 2012 (UTC)Reply
The extension also doesn´t work if there is a "." oder "-" or so on in pagename. 80.149.179.4 13:41, 5 March 2013 (UTC)Reply
I tried here:http://demo.flexdms.com/wiki/index.php/Department-2. This page has '-' in page name. Login as test21/123456. You will see access is denied. So it works for page with '-' in name. By the way,please ask support in Semantic Mediawiki mail listing. I mayh not monitor this extension page. Jasonzhang (talk) 16:37, 5 March 2013 (UTC)Reply

has SemanticAccessControl been tested againt hacking ?

[edit]

Hi,

First Thank you for this extension that SemanticMediaWiki nedded. Do you know if SAC (and its protected pages from viewing) was widely tested against hacking by unauthorised user ?

Thanks,

Nicolas NALLET (talk) 09:32, 18 October 2012 (UTC)Reply

It is not tested for hacking. As a general warning from mediawiki, it is not a secure system. Jasonzhang (talk) 13:13, 22 February 2013 (UTC)Reply

Create User Failure

[edit]

I screwed up when I installed SemanticAccessControl. I imported the pages I created on the development server onto the production server before I enabled the extension. I think I got most of the users granted with the appropriate permissions when I tried to add a new user with "create user" I get the following error. I did run the update.php script. I commented out the semanticaccesscontrol and tried to add the user and I still have the same error below.

Any ideas? Thanks! Amblerllc


A database error has occurred. Did you forget to run maintenance/update.php after upgrading? See: http://www.mediawiki.org/wiki/Manual:Upgrading#Run_the_update_script Query: INSERT INTO `user` (user_id,user_name,user_password,user_newpassword,user_newpass_time,user_email,user_email_authenticated,user_real_name,user_options,user_token,user_registration,user_editcount) VALUES (NULL,'AdminCary',,,NULL,,NULL,,,,'20121106014316','0') Function: User::addToDatabase Error: 1054 Unknown column 'user_options' in 'field list' (localhost) 66.41.96.6 01:46, 6 November 2012 (UTC)Reply

As I know, this error is not related to SemanticAccessControl. SemanticAccessControl does not manage user itself. Jasonzhang (talk) 13:12, 22 February 2013 (UTC)Reply

Class 'SMWSQLStore3' not found?

[edit]

php importTextFile.php Property\:ACL_Grant then: PHP Fatal error: Class 'SMWSQLStore3' not found in extensions/SemanticMediaWiki/includes/SMW_GlobalFunctions.php on line 286

ps: MediaWiki 1.20.2 PHP 5.4.1 (apache2handler) MySQL 5.5.23-log Semantic MediaWiki (1.8) P.swiki (talk) 14:06, 12 December 2012 (UTC)Reply

PHP Notice: Undefined index: ACL UserGroup in extensions/SemanticAccessControl/ACL.php on line 495,
PHP Notice: Undefined index: in extensions/SemanticAccessControl/ACL.php on line 502
PHP Notice: Undefined index: ACL Permissions in extensions/SemanticAccessControl/ACL.php on line 879, P.swiki (talk) 14:25, 12 December 2012 (UTC)Reply
SemanticAccessControl is updated with the latest SemanticBundle. I also have live demo for this extension. Check out the documentation for live demo. Jasonzhang (talk) 13:11, 22 February 2013 (UTC)Reply

Support Note

[edit]

For support, please send email to user mail list in SemanticMediawiki. I may not monitor this page. Jasonzhang (talk) 12:16, 25 February 2013 (UTC)Reply

Is it possible to protect against reading every pages in namespaces Template, Property, Special ?

[edit]

Thanks, Nicolas NALLET (talk) 09:24, 17 December 2013 (UTC)Reply

Template and Property are Schema page and only editable by User in Developer Group. Special page is not protected by this extension. This extension is targeted for content page instead of the pages above 207.102.70.3 16:48, 17 December 2013 (UTC)Reply

Content of UserGroup:SiteAC

[edit]

what content needs to page "UserGroup:SiteACL" to work the Access control?, which semantic properties i have to define into the "Template:ACL Page User Permission"

i hope can help me CrystianMarquez (talk) 17:14, 16 December 2014 (UTC)Reply

Google Code Shutting Down

[edit]

Hello, As you are likely aware, Google is shutting down their Google Code service in January of 2016. This extension appears to house its code with Google Code and is at risk to creating broken links and confusion of users in the near future.

I’m helping to let folks know about this coming update and provide some helpful links to make this migration easy. I hope you’ll take a moment and migrate your extension to a new hosting solution.

For extensions that have a compatible license, you can request developer access to the MediaWiki source repositories for extensions and get a new repository created for you. Alternatively, you may also export your code to other popular repositories such as Github and Bitbucket. Google has provided tools to help with this migration. Ckoerner (talk) 17:20, 7 July 2015 (UTC)Reply

For the record: I have just moved the code over from Google to GitHub to preserve it an have a smooth migration process. However, this extension is still unmaintained, so who ever wants to pick up this task is very welcome to do so. [[kgh]] (talk) 14:40, 7 December 2015 (UTC)Reply