I upgraded Confluence to 6.0.1. Also I use Crowd for SSO. All worked fine before upgrade. After upgrade it seems work good too, I can login into Confluence. But I the following WARNs have appeared in atlassian-confluence.log:
WARN [Caesium-1-4] [client.hash.reader.RemoteHashingInstructionsReader] readInstructions Unable to read remote instructions with key 'uid.onewayhash'.
WARN [Caesium-1-4] [analytics.client.hash.BcryptAnalyticsEmailHasher] create No instructions for hashing could be found.
What do this WARNs mean? How I can fix that WARNs?
I tried to search the solution in internet, but did not find anything useful.
Confluence collects analytics data about how you use the platform and reports it back to Atlassian. These warnings are part of that analytics package.
One way to get rid of these warnings is to turn off analytics.
Go to Confluence administration | General Configuration | Analytics and turn it off there.
More info on Atlassian's data collection policy.
Related
I want to make use of AWS SSO and integrate it to work with G suite.
I followed the official blog post - https://aws.amazon.com/blogs/security/how-to-use-g-suite-as-external-identity-provider-aws-sso/
However, I'm unable to perform the user synchronization from G suite into AWS SSO via the mentioned ssosync project - https://github.com/awslabs/ssosync. There's an open issue regarding the fact that ssosync is no longer available in AWS Serverless Application Repository. I've tried to clone and build the project manually but I get a 404 error and I can't find a reason why.
I am also unable to find a way to create users/groups programmatically (didn't find anything useful in AWS SSO API reference) in AWS SSO.
Has anyone encountered this problem as well?
I think that does not work anymore. What about using this one instead?
https://github.com/awslabs/ssosync was updated to V.2.0.0 few days ago (Dec 2022).
I installed it from AWS Serverless Application Repository and it seems to work.
It requires that you configure every possible variable before successful execution. For variables that you don't wish to use, put *.
We have SugarCRM Enterprise, Version 7.10.2.0 (On-Demand) and tried to install latest version (v1.5.62) of DocuSign plugin (https://sugarexchange.sugarcrm.com/apps/188/sugar-connector-to-docusign) on SugarCRM.
We followed the installation documentation (https://help.upcurvecloud.com/sugardocusign/Sugar_Connector_to_DocuSign.pdf)
Issue: Once we try to login then Error popups "DocuSign Error!" (Screenshot attached)
Any help will be highly appreciable.
Regards
In your Sugar instance go to Administration -> System Settings -> View Log and check the log for FATAL messages during the attempted login time.
E.g. a possible fatal message could be [FATAL] Platform name violation: unknown platform (<used platform name of connector goes here>).
Since Sugar 7.10 the platform parameter during authorization is limited to platforms known by your instance. Unknown platforms will be rejected and authorization will fail.
This could be the problem if the connector has yet to be updated for this new behavior.
If so either the provider of the connector or you should add the platform to the instance. E.g. by adding the file custom/Extension/application/Ext/Platforms/docusign_connector.php with contents:
<?php
$platforms[] = '<used platform name of connector goes here>';
However this is just a guess of what the problem could be as I have not seen your Sugar's log.
If your have any other fatal error messages, feel free to share.
Edit: Actually the platform enforcing seems to be a 7.11 thing rather than a 7.10 thing. So even if you do see an error as described above, it could only to be a warning (for future version compatibility reasons), rather than the actual source of the problem experienced by you.
So make sure to look for other errors as well.
I've installed the latest W-Systems DocuSign module for SugarCRM and I followed the installation guide to the T (https://www.w-systems.com/media/DocuSign/SugarConnectortoDocuSign_InstallationUseGuide.pdf). However, my problem start at the end of page 7 where I click "Configure DocuSign" or "DocuSign User Settings > Log In". Nothing happens.. no error message, no dialog window, nada.
I've run "Rebuild JS Grouping Files", "Quick Repair and Rebuild", cleared the cache and tried multiple browsers.
Has somebody else encountered this problem? Any suggestions on how to solve it?
EDIT: I was able to use the module without problems on a co-workers machine, but I still cannot use it on my own.
The SugarCRM <-> DocuSign Connector is written and maintained by SugarCRM, not DocuSign. The only integrations (Connectors) that DocuSign implements and maintains are its integrations with Microsoft, Google, and Salesforce.
With that said, if you're running into bugs/issues with the connector you'll need to contact SugarCRM and go through their support to resolve.
After being in contact with W-Systems support, they found out (by looking at the debug logs) that the database tables hadn't been correctly set up. The problem was fixed by uninstalling the module (without removing the tables), reinstalling the module, Admin > Quick Repair and Rebuild, and finally hard refresh (for me Ctrl+F5).
Everything now runs normally.
I'm trying to install IBM Eclipse tools for Bluemix but getting this error:
An error occurred while collecting items to be installed session
context was:(profile=epp.package.jee,
phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=,
action=). Unable to read repository at
http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/updates/wdt/kepler/plugins/com.ibm.ws.st.common.core_1.0.100.v20150220_1740.jar.
Connection reset
I tried to use solution from this dW Answers post Downloading Bluemix plugin for Eclipse... Is it even possible??? but it didn't help.
When I went and tried to manually download file by using this link : http://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/updates/wdt/kepler/plugins/com.ibm.ws.st.common.core_1.0.100.v20150220_1740.jar I get an error:
This webpage is not available
But when I changed link to use https as following, it works:
https://public.dhe.ibm.com/ibmdl/export/pub/software/websphere/wasdev/updates/wdt/kepler/plugins/com.ibm.ws.st.common.core_1.0.100.v20150220_1740.jar
So, my question is how can I redirect all "problematic" links to correct web site? In other words, is it possible to one url to another url?
Thank you.
UPDATE:
Tried to install this plugin at home and everything worked. I suspect that something wrong with a network on a work, will ask our admins to try to investigate the issue and post it back if we'll discover something interesting.
UPDATE 2
Confirmed by admins. It was a temporary network issue.
here is the last updated guide for Eclipse Bluemix tool plugin, which should be always used to install this plugin for the first time, in order to be sure on using the right version
https://www.ng.bluemix.net/docs/#manageapps/eclipsetools/eclipsetools.html#eclipsetools
At the following url a shorted version with Eclipse installation link:
https://www.ng.bluemix.net/docs/starters/deploy_eclipsetools.html
Your issue could be related to an obsolete reference updated with a new release version for the plugin.
I'm having difficulty in integrating AEM 5.6.1 with Site Catalyst. It allows me to connect in the configuration successfully, but does not work on the framework setup.
I've followed the standard procedure to connect AEM to SC and it accepts my login in the configuration, but fails on the framework set up with the browser message 'We were not able to login to SiteCatalyst. Please check your credentials and try again.'. Behind the scenes in the server log;
12.12.2014 14:10:06.967 *WARN* [0:0:0:0:0:0:0:1 [1418393406764] POST /libs/cq/analytics/sitecatalyst/service.json HTTP/1.1] com.day.cq.analytics.sitecatalyst.impl.SitecatalystHttpClientImpl Data center 'https://api3.omniture.com/admin/1.3/rest/' responded with errors {"error":{"code":500,"message":"Internal Server Error"}}
12.12.2014 14:10:06.967 *ERROR* [0:0:0:0:0:0:0:1 [1418393406764] POST /libs/cq/analytics/sitecatalyst/service.json HTTP/1.1] com.day.cq.analytics.sitecatalyst.impl.servlets.SitecatalystServlet Call to SiteCatalyst method 'Company.GetReportSuites' failed com.day.cq.analytics.sitecatalyst.SitecatalystException: not authenticated
I've tried accessing via the API Explorer and it works.
I've tried the troubleshooting guide without success.
I can log in to Site Catalyst, I'm an admin, I am in the web services access group.
I've tried using a clean install of CQ5.6.1 with geometrixx - it doesn't work either.
I've tried this from a server and from a localhost/dev machine with the same results. No proxy. I've even tried using the shared secret as the password but then it doesn't connect at all, and fails on the configuration screen.
What might cause this to fail?
If it doesn't work with a fresh install and Geometrixx, then it's probably an Adobe bug. That's typically the first thing support will ask you about.
I would also verify using Geometrixx Outdoors, or a more recent demo site, on your fresh install, just to ensure it's not an outdated ClientLib issue.
I know this isn't a direct answer to your question, but honestly, I would approach the integration differently. I've worked with the AEM-SC framework and it's buggy at best. It's very finicky, it doesn't REALLY work the way the documentation claims, and it requires that you're very specific about what Clientlibs are on the page.
Moving forward, I think using Adobe Dynamic Tag Manager is the better approach, for many reasons. My understanding is that it's Adobe's recommendation as well. I'd consider moving to that. In AEM 5.6.1, you'll have to customize your integration with DTM, but it's not very hard.
Solution: Add a property on the configuration node for sitecatalyst: (eg. /etc/cloudservices/sitecatalyst/my-sc-configuration)
server=https://api.omniture.com/admin/1.2/rest/
it also seems to work with newer API versions such as https://api3.omniture.com/admin/1.3/rest/
It would appear that for 5.6.1 it ignores the OSGi configuration, at least for the configuration screens. With this extra property, the framework page loads without error and allows selection of the RSID.