@crich2784 In the OSGi stack, CQ-DAM-Handler-Gibson Font Manager
configuration handles the fonts. Go to
http://[server]:[port_number]/system/console/configMgr and edit
"CQ-DAM-Handler-Gibson Font Manager Service". Add the path to your font
library "C:\Adobe\CustomFonts" or you can add the font to "[AEM Install
Dir]/crx-quickstart/fonts". Hope this helps!
@ThomasRognoni Seems to be a sync issue as your colleagues are able to
see the artifacts so the fragments are part of the server for sure. If
you (or the user used to log in) have the same permissions as your
colleagues so you can check for the missing artifacts under this path on
your local- C:\Users\\Workbench 6\\\.
Ideally, you should be able to find the missing files under this path to
be able to load those on the workbench.
@rajatkumar When you enable global security on the WebSphere Application
Server, it throws a ‘j_security_check’ exception on login to /lc.
Therefore, it is recommended to install the following package on the
WebSphere Application Server if global security is enabled. It's not
actually a bug but a known issue with WAS (Global Security). Also, the
two steps shared above are already part of the package in the form of
configs so I assume the package (or the correct package) was not
applied. More inf...
@rajatkumar Thanks for confirming! Next, do check the below checkpoints
if these are modified with the content patch or not. Looking closely at
the package name shared, I see that package
AEM-FORMS-6.5-WEBSPHERE-GLOBALSEC-CONFIG should be installed for AEM
Forms 6.5 JEE so you can recheck. Also, you need to disable Global
Security on the WebSphere Application server before applying this patch
and re-enable it later. 1. Does "Adobe Granite Token Authentication
Handler" bundle in configMgr page sh...
@rajatkumar Could you check for the below configuration on this set-up
and ensure that CSIv2 inbound/outbound transport option to
SSL-Supported. On the default Global Security enabled installation of
IBM WebSphere, CSIv2 inbound transport option is usually set to
SSL-required. To change the option:1) Log in to IBM WebSphere
administration console.2) Expand Security, and then click Global
security.3) In the Authentication section, expand RMI/IIOP security, and
then click CSIv2 inbound communicati...
@mynyl If you review the stack, its evident that the issue is specific
to target host so please review the URL settings configured. You can
check the protocol as well, i.e a complete URI along with https.  -
Caused by: org.apache.http.ProtocolException: Target host is not
@mynyl I see the refresh_token_uri and access_token_uri set as nulloauth
in the URL. You can cross-check the redirect URL in the OAuth settings
for the Adobe Sign application, the URL copied should have the actual
server name. Also, 1. Was this working correctly before or it's a new
set-up?2. Was there any change on the server after which this issue
happened?Please share the complete error stack for review, if the issue
persists after updating the server name.  -
@Vani1012 We don't look into issues related to adobe credential manager.
You can drop an email to firstname.lastname@example.org with your query or refer to
@LYUAN FYI - All AEM artifacts are now available via Maven Central
and the adobe-public profile is not needed so you may have to update the
repository URL. More information here  -