nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Image authentication... repeated requests for login/password

n0hr

We have an annoying issue that needs to be resolved.

When we publish an image to the document library and then embed that image in a wiki (or blog?) users are re-asked for their login/password information.

For example, if an end user opened a wiki page that contained 3 images, the user would be prompted for username/password 3 times (once for each image).

Our alfresco-global.properties file contains:

authentication.chain=alfrescoNtlm1:alfrescoNtlm,passthru1:passthru,ldap1:ldap-ad
ntlm.authentication.sso.enabled=false 
alfresco.authentication.authenticateCIFS=false 
ntlm.authentication.sso.enabled=false 
passthru.authentication.authenticateCIFS=true 
ldap.authentication.active=false 
ldap.synchronization.active=true 
‍‍‍‍‍‍‍‍‍

What can we do to correct this?

Find more posts tagged with

Comments

shazada

I have the same issue in Alfresco 3.1.2 & 3.2.

I can only select a image from the image library.

n0hr

The only way I've found to display images without prompting for user/password in Alfresco Share (Wiki) is to embed images that are NOT stored in Alfresco - which defeats the purpose.

Does the Alfresco team have a solution?

n0hr

Shall I assume that unless I want to greatly annoy my users with login prompts I must store images used in Wikis outside of Alfresco?

That's a frustrating solution.

Does SharePoint handle this properly?
Any other solutions?

kevinr

I've just tried this and i can't reproduce the issue with latest 3.2. I added some images to the doclib, created a new wiki pages, inserted the images using the Image Library and also directly by inserting the links, no repeated requests occur.

I assume from your global.properties that you are only using standard alfresco authentication?
Can you view source from the page and copy/paste the wiki part of the page output into a forum post?
Do your end users view the wiki pages directly in Share?

Cheers,

Kev

n0hr

Thanks for the reply Kev…

I'm primarily using standard alfresco authentication. That is, I'd like to setup ldap but that's not yet working. For example, I see this issue even with an account called "admin" which is authenticated via standard alfresco (but not in ldap).

I should point out, that if I create a wiki page and direct link to the pages in the doclib, I don't see the issue if I refresh the page myself. However, if I login under another browser & account, then I see the issue immediately. Once I enter the login/password info (repeatedly), then it works ok.

This is in Share (the only way my end users access the wiki).

Here is an example html snippet:

<img src="../../../proxy/alfresco-feed/api/node/content/workspace/SpacesStore/366155d4-1836-4522-a84d-d90899cbfa3c/S4.png" alt="" width="1015" height="760" />
‍‍‍

This link was generated by image insert and pasting the link found on the Document URL field.

By the way, I had pasted the full (absolute) URL which starts with http:// etc. - but alfresco automagically updates it to a relative link (../../../) for some reason. I don't know if that's a clue. Maybe not.

Any ideas?

n0hr

Loading images rather than using the document library URL seems to help.

kevinr

It's the "alfresco-feed" part of the URL that is the problem - that is a different authentication route than just "alfresco". That requires HTTP Basic Auth - and should really only be used for external things like pasting a link in an email etc. If you use the image insert library tool like you say then it should insert links with just "alfresco" in them - this uses the standard authentication route - the same one that the current page is using i.e. cookie based authentication/ntlm or whatever you have setup.

Cheers,

Kev

shazada

Use SSO.

I've configured SSO and the user doesn't need to login each time. I know this is crappy, but if you don't have it, maybe it's worth looking into.