Im presently trying to configure LDAP to work with my AEM install.
im working with version 6.4 and i did follow the steps found here:
To provide the configManager the LDAP server info. as far as i can tell it looks ok, but now, i want to test this out.
What i'm trying to achieve is that when people access my forms portal, they wont be asked to provide a username and password.
How can i set this up now, so that i no longer see the login page?
Thank you very much,
Thx again for the new notes, and yes I can modify the page, but the SAVE doesn't work. tried it in firefox and chrome. when I go back to it, the changes are not applied
That is not correct - there is an issue with your AEM instance. What version are you running. All Config screens must be able to save these values.
Can you try this on a fresh AEM DEV instance. Then we can see what action we can take to address the issue of your config values not saving (we may have to look at possible hotfix)
I followed the entire new artilce on 6.4 - and logged into AEM as the LDAP user - LAM.
Alright, before I do another install, I want to make sure that were on the same page
when you go to the OSGI configMgmt screen, do you use this exact URL:
or another URL?
I'm using this one:
Are we on same page?
Alright, and correct me here if im wrong, but when you see the 4502 port, were talking about the OSGI only install?
And if we see 8080 port, its the JEE full install that also includes an OSGI component, correct?
Correct - if you are using AEM Forms - that would be correct!
perfect, with that said now and before I re-install every thing again (big long process), can Adobe confirm that the issues I have of not saving could be related to me using the JEE/OSGI install instead of the OSGI? maybe this change in the way the GUI's are behaving actually comes from the way they were design by Adobe? (which are 2 slightly deferent sets of GUI interfaces on each side)
I'm seeing quite a few instances thus far, between documents explaining things using OSGI that are not really transferable to JEE/OSGI.
and this could be a good way to confirm if this has been the purpose since the get go. (from the DEVS, developing 2 slightly different interfaces)