Eclipse Community Forums: Oomph » Form-based authentication with gitlab 13.6.1 not working because of missing closing tag for "me

Home » Eclipse Projects » Oomph » Form-based authentication with gitlab 13.6.1 not working because of missing closing tag for "me(After upgrade from gitlab 13.3.8-ce to 3.6.1-ce the authentication fails because of a sax parser exception caused by a missing closing tag for "meta" )

Form-based authentication with gitlab 13.6.1 not working because of missing closing tag for "me [message #1835154]

Wed, 25 November 2020 15:57

Eclipse User

No Message Body

Attachment: .log
(Size: 37.01KB, Downloaded 143 times)

Re: Form-based authentication with gitlab 13.6.1 not working because of missing closing tag for &quo [message #1835157 is a reply to message #1835154]

Wed, 25 November 2020 22:37

Eclipse User

I assume you found out to use that via this:

https://wiki.eclipse.org/Eclipse_Oomph_Authoring#Accessing_Setups_that_Require_Authentication

But I can't debug such a thing for you because I don't have a password on your server.

Some things you could try yourself (in addition to debugging it). The -Doomph.setup.ecf.trace=true will show more details about the network traffic.

Delete everything in <home>/.eclipse/org.eclipse.oomph.setup/cache and then you can see what files are downloaded from the server and see what is wrong with the XML being processed. It sound like at some point an XML file is expected and likely a HTML has been served instead.

Re: Form-based authentication with gitlab 13.6.1 not working because of missing closing tag for & [message #1835601 is a reply to message #1835157]

Tue, 08 December 2020 04:42

Eclipse User

I looked into the issue and the underlying problem is that the used Xerces SAX parser assumes valid XML but gitlab uses HTML5 which is less restrictive compared to XML. While XML demands a closing tag HTML5 does not for the "meta" tag. I didn't find any option to relax the XML validation in Xerces.
For increase of robustness it would be preferable to use TagSoup instead of Xerces for parsing HTML websites.

Re: Form-based authentication with gitlab 13.6.1 not working because of missing closing tag for & [message #1835646 is a reply to message #1835601]

Wed, 09 December 2020 07:21

Eclipse User

I'm confused by the above statement because org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl.FormHandler.readForm(URI) reads the bytes and uses pattern matching to find the form details (assuming the bytes are UTF-8 encoded). It does not parse the site content at all. Of course the setup resources themselves must be well-formed XML, so I'm not sure when/how HTML5 enters the picture...

Re: Form-based authentication with gitlab 13.6.1 not working because of missing closing tag for & [message #1835676 is a reply to message #1835646]

Thu, 10 December 2020 03:22

Eclipse User

Interesting. In the attached log file of the initial post there is the following stacktrace starting at line 11:

org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.xml.sax.SAXParseExceptionpublicId: https://git.nia-health.de/nia/nia-backend/-/raw/master/eclipse/NiaBackend.setup?oomph_form=b%27users/sign_in%27#/; systemId: https://git.nia-health.de/nia/nia-backend/-/raw/master/eclipse/NiaBackend.setup?oomph_form=b%27users/sign_in%27#/; lineNumber: 69; columnNumber: 3; The element type "meta" must be terminated by the matching end-tag "</meta>".

It looks like the SAX parser is involved when adding a URL to an Eclipse project via the "Add User Projects" Dialog.

Re: Form-based authentication with gitlab 13.6.1 not working because of missing closing tag for & [message #1835682 is a reply to message #1835676]

Thu, 10 December 2020 05:11

Eclipse User

If the form authentication fails, the setup URL will still be accessed and that will, without a proper cookie, likely redirect to some HTML failure page that will not be well-formed XML.

You could try using the VM option -Doomph.setup.ecf.trace=true to get more detailed information about the flow of information over the network. It can also be useful to clear the ~/.eclipse/org.eclipse.oomph.setup/cache folder and then to see which resource have been downloaded and what their contents are when you the try the installer or IDE again.

To really figure out what's going wrong, you'd need to actually debug org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl. It's easy to set up a development environment for that purpose...

Previous Topic:	ResourceCreationTask and line delimiter CRLF
Next Topic:	Installation Error

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jun 21 05:04:50 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter