I have just get-started with Alfresco Community Edition 5.0.0b and trying to do handshake with apache cmis to alfresco.
Referring to multiple sources and this doc http://ecmarchitect.com/images/articles/cmis/cmis-article.pdf
I am now able to authenticate through GET request at
http://<IP Address>:8080/alfresco/s/api/login?u=admin&pw=admin
and fetch the token for each successive request. I am looking for atom-public-url where I need to pass the username and password to move on with content management.
But, I am unable to hit cmis URL on alfresco. Tried multiple URLs like
http://<IP Address>:8080/alfresco/s/cmis
http://<IP Address>:8080/alfresco/api/cmis
and likewise, but nothing works so far.
I am getting 404 with following message each time
Message: 10140008 Script url /cmis does not map to a Web Script.
Any help appreciated! Please let me know if I missed anything ..
P.S. After the fresh install of alfresco I have by default 403 Web Scripts available but none with above matching /cmis
Those are the wrong CMIS endpoints for Alfresco 5.0. You instead need to use one of
http://localhost:8080/alfresco/api/-default-/public/cmis/versions/1.0/atom
http://localhost:8080/alfresco/api/-default-/public/cmis/versions/1.1/atom
Depending on if you want to use CMIS 1.0 or 1.1 support
You can find the per-Alfresco-version CMIS endpoint URLs on the Alfresco Wiki
Related
We are getting attached error while adding a relying party trust to ADFS. This needed to be done as our CRM Test server had to be repaired since it was not taking in new patches. We reinstalled CRM and were trying to reconfigure IFD when we are running into this issue
Error While Adding a Relying Party
While on the ADFS server, can you browse to the metadata address?
Does it result in an XML document?
I've seen this error when you have HTTP URL in the metadata. In which case, download the metadata, change to HTTPS and load as a file.
Failing that, can you add the RP manually?
We performed all the steps again and this time the File option worked for us. we were able to move forward by downloading the XML and use it.
I have been working with Kyle H. in Azure Support Chat and he recommended that I post this here.
Please be understanding, as I have read every related Stack Overflow post relevant and have exercised due diligence.
I have completely deleted and restarted both my Azure resources AND source code multiple times. Using this guide: https://learn.microsoft.com/en-us/azure/bot-service/bot-builder-howto-deploy-azure?view=azure-bot-service-4.0
The bot project is using the v4 template 'Echo'.
In Azure Portal, Test in Web Chat: "There was an error sending this message to your bot: HTTP status code Forbidden"
In Bot Emulator with ngrok configured: Cannot post activity. Unauthorized.
Following instructions here: https://learn.microsoft.com/en-us/azure/bot-service/bot-service-troubleshoot-authentication-problems?view=azure-bot-service-4.0#step-2
I ran: curl -k -X POST https://login.microsoftonline.com/botframework.com/oauth2/v2.0/token -d "grant_type=client_credentials&client_id=b7404e9f-0e74-4174-aa4f-447fdd96d7f0&client_secret=REMOVED&scope=https%3A%2F%2Fapi.botframework.com%2F.default" and I am returned a valid access token.
I have confirmed multiple times that my app registration is using https, as well as the /api/messages route, and that my app service has the two keys MicrosoftAppId and MicrosoftAppPassword and they are set appropriately. Including stopping and starting and the restart functionality. I have also ensured that during deployment(VS 2017 Publish), it removes existing files.
My last attempt was to upgrade the template 'Echo' bot to .net core 2.2 - which deployed successfully. I again verified app id and app password set as described above, and unfortunately both the Bot Emulator and Test in Web Chat failed with the same errors.
Edit 1:
I used 'Create new resource' and picked the 'Web App Bot' template. I chose the 'Echo' bot. I chose 'Automatically Generate Application ID and Password' as well. This resulted in a bot deployment that did not have authorization errors. However, I noticed that instead of a 'Bot Channel Registration' resource - it instead created a 'Web App Bot'. When inspecting 'Application Settings', application ID and password aren't present, yet it functions just fine.
Edit 2:
I researched deeper, and learned that the 'Web App Bot' created in azure uses the botFilePath and botFileSecret application settings and likely keeps the app id and app password there.
Edit 3:
There is a huge difference between the v4 BotBuilder EchoBot template you use in visual studio when creating a new project and the EchoBot template used in Azure when creating a new resource. Narrowing it down now.
Edit 4:
I was able to use the Azure created web bot and modify it to continue my work. Was not possible with the Vsix templates even with ensuring app config and .bot file config were correct.
Edit 5:
I also learned that v4 doesn't support Microsoft Teams - and that was the entire purpose of my endeavor. v3 documentation is near nonexistent. So I think I'll be using an entirely different framework to integrate with Teams. I even attempted to implement: https://github.com/OfficeDev/BotBuilder-MicrosoftTeams-dotnet but my bot only responds with "Sorry, there was a problem encountered with your request" in Teams.
Edit 6:
I managed to get my bot functioning with Microsoft Teams, during the process solving the unauthorized error.
I created the Echo bot in Azure - and used App Studio in Microsoft Teams to add a manifest and add the bot to our team.
After that, I imported the project located here: https://github.com/OfficeDev/BotBuilder-MicrosoftTeams-dotnet/tree/master/CSharp/Samples/Microsoft.Bot.Builder.Teams.TeamEchoBot
Then I modified setup.cs to work with the encrypted .bot file, based on the source code that created the Echo Bot in Azure.
The VSIX templates are going to generate Startup code that uses the .bot file for appId/secret and, when deployed to Azure, is going to be looking for an endpoint named "production" which you would have had to add yourself to the default .bot file with the appid and secret from your provisioned bot.
For more details, check out this previous answer I gave on this topic .
If you are struggling to deploy your bot, I would recommend looking at this guide. The steps will walk you through creating a bot on Azure, and then you can download the source code, develop your bot, and redeploy it.
Glad I could help!
i try to use rest api in kaa ver 0.10.0 but document is empty https://kaaproject.github.io/kaa/docs/v0.10.0/Programming-guide/Server-REST-APIs/
I use document in ver 0.9 but something not work.How i can reference rest api with kaa ver 0.10.0
Please share the error msg that you are getting. Mostly it's a case of incorrect appender config or field name mismatch with those mentioned in your DB. I was facing following errors with REST log appender but was able to solve them as mentioned below:
Error 500: I found two errors with my configuration of RestLogAppender in the admin panel. First, I had put http:// before my host. Had to remove the same. Second, I should have mentioned Relative URI path starting and ending with a forward slash /.
Error 400: I had given slightly different names to the JSON fields in the Django models. The sequence of the fields did not matter but the name of fields did matter.
I used this API http://docs.kaaproject.org/display/KAA/Admin+REST+API#AdminRESTAPI-Getuserprofile and was successfully able to use it. Please specify the specific problem you are facing?
Edit: and dont forget to check the api using PostMan if you find any issue.
The Kaa 0.10.0 documentation server REST API uses JS scripts that are hosted on third-party servers. Unfortunately, those servers are now down and that is why the REST API documentation page is rendered empty at the moment.
Kaa team has already prepared a fix for this. The respective JS files will be hosted along with the documentation. But, this requires some additional work to be done before the updated documentation become available.
I am using LiveSDK 5.6 to get file and folder info stored in One Drive. I am able to get these info, but Now, I am trying to find file version history. I am not able to find a way to get version history of a file stored in One Drive.
Can anyone suggest me a way to get version history of a file (using Live SDK or REST API ?
Rest API documentation API: https://msdn.microsoft.com/en-us/library/dn659752.aspx
Thanks in advance.
The LiveSDK, unfortunately, won't return version history but will return created_time, updated_time, etc. The new OneDrive API has a new feature for checking changes made to an item and its children (http://onedrive.github.io/items/view_changes.htm).
As Toan-Nguyen says, we can't get version number from One Drive APIs now (July 8 2016).
https://dev.onedrive.com/resources/item.htm
I want to get file version information from API, so I requested from Request page. If you want to get version, please vote.
I am trying out a mashup of Alfresco and ProcessMaker. I intend to use Alfresco's document management capabilities over ProcessMaker.
Here is the scenario:
A user fills up a form in ProcessMaker and a file is uploaded in Alfresco.
I followed the wiki in this link. The problem is that, my result variable is always false. I also checked my input. I am able to access Alfresco via the address I provided, but it still does not work. I also ensured that the file exists in my directory.
Is there a way I can check (probably from logs or console) the error being returned by Alfresco or ProcessMaker so I can continue?
Alfresco is installed in a Japanese version of Windows 7.
Alfresco version is 4.2.c.
Process Maker version is 2.0.45.
I have no experience with ProcessMaker, but here's a couple of things you can try to investigate your issue:
inspect the network traffic between ProcessMaker and Alfresco (e.g. with Wireshark) to see if there's any hint available in the HTTP responses from Alfresco
enable DEBUG logs on Alfresco side
as far as I can see, ProcessMaker users Alfresco CMIS REST APIs to implement its triggers. Have a look at class.pmAlfrescoFunctions.php in ProcessMaker and try the calls yourself with some REST client (e.g. curl, Chrome REST console, htty)
This should give you an idea of what's going wrong in your case.
UPDATE
After reading that the Japanese language pack changed a folder name from "Sites" to "/サイト", and double checking the Alfresco triggers code, it's indeed the case that localized versions of Alfresco are not supported OOTB by ProcessMaker, which hardcodes "Sites" in its CMIS queries.
While the workaround provided by #nmenego would be enough in most cases, I opened a bug to ProcessMaker to let them know of the limitation.
I discovered that the problem was in the encoding used by my installed Alfresco. Instead of the default folder /Sites, the default directory was /サイト (sites in Japanese). Apparently, upon installation, the names of the default folders are translated to Japanese.
What I did was I added a folder named /Sites, and it all works now.
Of course, the points pointed out by skuro are all valid as well.
We just confirmed that this is a bug in the ProcessMaker connector triggers for Alfresco, thank you for reporting it.
I've just opened ticket 11003 in ProcessMaker's Main Support Portal for the developers to work on fixing it.
Please register for free in ProcessMaker's Main Support Portal in order to follow up on the resolution of this bug.
Best regards,
Arturo A. Robles
Customer & Partner Support Manager
Colosa Inc. - ProcessMaker