Yes, I can edit them and find that object...I'm trying deleting those users and retrying to login, it still hangs...I think I understand where is the error (please check the second log file): those users are created because xwiki hangs on the first login and something goes wrong (and very slow) during the database saving, an user (or browser) makes a second call and Xwiki finds an already present user but not "complete" ,so tries to create another one.
How can we fix this situation (database)?
Thank you
[logSnippet2.txt](https://discourse.xwiki.org/uploads/default/original/1X/6c… (35.3 KB)
---
[Visit Topic](https://discourse.xwiki.org/t/ldap-login-issue/226/5) to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click here](https://discourse.xwiki.org/email/unsubscribe/ec666aa06096063ac9fcc8e….
Not sure why you are talking about http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Authentication#HKerbero… since you example does not have anything to do with it (which is good).
So back to you example now, if manual login works you probably don't need much on XWiki side.
[quote="Johannes, post:1, topic:179"]
I could not see it in the tomcat logs, only that the "user is null"
[/quote]
So if mod_auth_kerb. is doing it's job you should see in the LDAP debug log something like: "RemoteUser: toto(a)mydomain.com" or "RemoteUser: mydomain.com\toto" or some other format (that's why you have to provide a regexp in the configuration) which is the REMOTE_USER that XWiki is supposed to receive from whatever is in front of and and parsed with "xwiki.authentication.ldap.remoteUserParser".
If you don't see it there is no much you can do at XWiki level. Sometimes bad authenticator module don't properly set the HTTP REMOTE_USER and instead set a custom HTTP header that you can indicate in `xwiki.authentication.ldap.httpHeader`. I don't have any experience with mod_auth_kerb sorry.
---
[Visit Topic](https://discourse.xwiki.org/t/help-setting-up-sso-with-kerberos-and-… to respond.
You are receiving this because you enabled mailing list mode.
To unsubscribe from these emails, [click here](https://discourse.xwiki.org/email/unsubscribe/53280ea1570d2ffb69246b6….
Hi
We have two objects of two different Classes, each on it's own page.
We looked, for a example,
http://platform.xwiki.org/xwiki/bin/view/DevGuide/APIGuide#HAccessobjectsin…
## get the document which has the object (only one here) - this is the page where I can see things in the object editor
## Retrieve the first object (index [0]) among all objects attached to the page MySpace.MyDocWithMyClassObjects and of a certain class MySpace.MyClass
#set( $MyDoc = $xwiki.getDocument("MySpace.MyDocWithMyClassObjects"))
## get the document wich contains the class definition: this page has entries in the class editor
#set( $class = $xwiki.getClass("MySpace.MyClass"))
#foreach($prop in $class.properties) ## go through all properties
* ${prop.prettyName} : $MyDoc.display($prop.getName())
#end
our implementation is a bit different as we have two objects to manage:
## first the object on this page ($doc)
#set($class = $doc.getObject('Sandbox.testClassOOPage1').xWikiClass)
#foreach($prop in $class.properties)
; $prop.prettyName
: $doc.display($prop.getName())
#end
## then the object (of a different class) on another page
#set($docClass2 = $xwiki.getDocument('Sandbox.testClassOOPage2Example') )
$docClass2
#set($objectOfClass2 = $docClass2.getObject('Sandbox.testClassOOPage2').xWikiClass)
#foreach($class2Prop in $objectOfClass2.properties)
; $class2Prop.prettyName
: $docClass2.display($class2Prop.getName())
#end
This works fine in view mode...
But the problem is that we also need EDIT mode (inline)
The form seems ok before saving , we have input controls for both objects (of different classes). We also see the data of both objects
But when I modify the data of the second object in the form and press SAVE & VIEW the modification is not saved...
How can we achieve our goal
Gerritjan Koekkoek
Vader van Rai Koekkoek (cdls) en voorzitter vereniging CdLS
Visit our website<http://www.cdlsworld.org>
Facebook<https://www.facebook.com/gerritjan.koekkoek>
email<gerritjan(a)cdlsworld.org>
Hi Everybody!
We went live with out XWiki last week, after three months of testing - and there is one issue about XWiki and GoogleAds.
Our Firewall blocks Googleads - every time when a user opens XWiki with the internet explorer there ist the security hint that
"there is no blocking information for the security certificate available".
When I click on "show certificate" I get the information, that the certificate has been issued for googleAds.
Does anybody know what XWiki has in common with googleAds and where I can prevent Xwiki from "telephoning" home?
The Window with that hint appears everytime when xwiki is opened in a new IE-Window...
Thanx in advance...
Toby :)
- if anyone needs a script for the database-plugin for creating searchable phone-list - just write me :)! Ill send you the source-code
Hi everybody,
I'm migrating content from 5.4.5 wiki to the 9.4. The old content was one
space and about 300 pages. The content has been imported ok, however it is
visible only to admin.
Is there any debug option which I can turn on, so I can debug why is this
page restricted to other users?
Thanks for hints.
--jans
Greets,
In my XWiki installation, when regular users log in for the 1st time, they are greeted with a simple message:
Error
You are not allowed to view this page or perform this action.
To be sure, the user has no rights at all. However, the new user IS placed in the group "XWikiAllGroup", and that group DOES have all rights excelt Admin, Delete, and Program. In other words, it has View, Comment, Edit, and Script, and Register.
1. Is this correct? Should the new user not have all rights except for Admin, Delete, and Program?
2. The new user IS placed in the XWikiAllGroup. So, why can the new user not see the Main page, and other pages?
3. What have I done to get in this situation and what is the proper remediation?
Thanks!!!
Doug
The information contained in this transmission may contain West Marine proprietary, confidential and/or privileged
information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are
hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited.
If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original
message. To reply to our email administrator directly, please send an email to netadmin(a)westmarine.com.