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.

webclient action repository credentials

smola

Hi,

I'm tying to write a web client action using JCR. I managed to get the repository bean in my ActionExecuterAbstractBase derived class by adding a JCR.Repository bean reference in my model-context file and adding a setter method for the bean.

The problem is that I don't know how to login to the repository with the current user's credentials!? Can it be done or do I have to use a predefined login credentials?

When I use the foundation API in my action it doesn't need to login.

Any ideas, please?

Thanks

Find more posts tagged with

Comments

marcus

How'd you go with this? I thought I'd have a play with JCR from an existing customisation of the web-client, but can't figure out how to login using the existing user stored in the authenticationService.

davidc

The JCR spec. requires a login call in order to get a JCR Session.

Right now, there isn't a way to JCR login using the currently authenticated user via the JCR public interface. You can raise a JIRA feature request if you want this.

However, there is a backdoor approach - I haven't tried it personally, but it should work.

SessionImpl sessionImpl = new org.alfresco.jcr.session((RepositoryImpl)repository);
sessionImpl.init(authenticationService.getCurrentTicket(), "SpacesStore", null);
Session session = (Session)sessionImpl;
‍‍‍‍‍

The above code assumes you have injected JCR.Repository into 'repository' and AuthenticationService into 'authenticationService'.

There is no need to call session.logout(). In fact, you shouldn't in this scenario. Also, all calls to session will inherit the currently open transaction.