<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Alfresco ECM Core API returns 403 in Alfresco Forum</title>
    <link>https://connect.hyland.com/t5/alfresco-forum/alfresco-ecm-core-api-returns-403/m-p/92190#M27326</link>
    <description>&lt;P&gt;Your OPTIONS request is not sending any authentication header with the ticket that I can see. So even though you have authenticated before, this call is again unauthenticated and thus a 403 is expected.&lt;/P&gt;</description>
    <pubDate>Fri, 24 Apr 2020 14:01:51 GMT</pubDate>
    <dc:creator>afaust</dc:creator>
    <dc:date>2020-04-24T14:01:51Z</dc:date>
    <item>
      <title>Alfresco ECM Core API returns 403</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/alfresco-ecm-core-api-returns-403/m-p/92189#M27325</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I'm calling following API using admin credentials from Angular&lt;/P&gt;&lt;PRE&gt;http://localhost:8080/alfresco/api/-default-/public/alfresco/versions/1/nodes/-root-/children?skipCount=0&amp;amp;maxItems=100&amp;amp;relativePath=Sites/rtc/documentLibrary/attachments&amp;amp;includeSource=true&lt;/PRE&gt;&lt;P&gt;but it returns 403 when browser sends OPTIONS request. I've already configured CORS in tomcat's web.xml but still it returns 403. I'm able to authenticate using tickets API.&lt;/P&gt;&lt;P&gt;Here are the CORS settings&lt;/P&gt;&lt;PRE&gt;&amp;lt;filter&amp;gt;
		&amp;lt;filter-name&amp;gt;CorsFilter&amp;lt;/filter-name&amp;gt;
		&amp;lt;filter-class&amp;gt;org.apache.catalina.filters.CorsFilter&amp;lt;/filter-class&amp;gt;
		&amp;lt;init-param&amp;gt;
			&amp;lt;param-name&amp;gt;cors.allowed.origins&amp;lt;/param-name&amp;gt;
			&amp;lt;param-value&amp;gt;http://localhost:4200,http://localhost:4201,http://localhost,http://127.0.0.1:4200,http://127.0.0.1&amp;lt;/param-value&amp;gt;
		&amp;lt;/init-param&amp;gt;
		&amp;lt;init-param&amp;gt;
			&amp;lt;param-name&amp;gt;cors.allowed.methods&amp;lt;/param-name&amp;gt;
			&amp;lt;param-value&amp;gt;GET,POST,HEAD,OPTIONS,PUT,DELETE&amp;lt;/param-value&amp;gt;
		&amp;lt;/init-param&amp;gt;
		&amp;lt;init-param&amp;gt;
			&amp;lt;param-name&amp;gt;cors.allowed.headers&amp;lt;/param-name&amp;gt;
			&amp;lt;param-value&amp;gt;Content-Type,X-Requested-With,accept,Origin,Access-Control-Request-Method,Access-Control-Request-Headers&amp;lt;/param-value&amp;gt;
		&amp;lt;/init-param&amp;gt;
		&amp;lt;init-param&amp;gt;
			&amp;lt;param-name&amp;gt;cors.exposed.headers&amp;lt;/param-name&amp;gt;
			&amp;lt;param-value&amp;gt;Access-Control-Allow-Origin,Access-Control-Allow-Credentials&amp;lt;/param-value&amp;gt;
		&amp;lt;/init-param&amp;gt;
		&amp;lt;init-param&amp;gt;
			&amp;lt;param-name&amp;gt;cors.support.credentials&amp;lt;/param-name&amp;gt;
			&amp;lt;param-value&amp;gt;true&amp;lt;/param-value&amp;gt;
		&amp;lt;/init-param&amp;gt;
		&amp;lt;init-param&amp;gt;
			&amp;lt;param-name&amp;gt;cors.preflight.maxage&amp;lt;/param-name&amp;gt;
			&amp;lt;param-value&amp;gt;10&amp;lt;/param-value&amp;gt;
		&amp;lt;/init-param&amp;gt;
	&amp;lt;/filter&amp;gt;
	&amp;lt;filter-mapping&amp;gt;
		&amp;lt;filter-name&amp;gt;CorsFilter&amp;lt;/filter-name&amp;gt;
		&amp;lt;url-pattern&amp;gt;/*&amp;lt;/url-pattern&amp;gt;
	&amp;lt;/filter-mapping&amp;gt;&lt;/PRE&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="acs.png" style="width: 999px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image"&gt;&lt;img src="https://connect.hyland.com/t5/image/serverpage/image-id/613i5E2A6052D558DDCF/image-size/large?v=v2&amp;amp;px=999" role="button" title="image" alt="image" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Kindly note that Docker container environment is used for ACS deployment&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2020 12:25:18 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/alfresco-ecm-core-api-returns-403/m-p/92189#M27325</guid>
      <dc:creator>zain</dc:creator>
      <dc:date>2020-04-24T12:25:18Z</dc:date>
    </item>
    <item>
      <title>Re: Alfresco ECM Core API returns 403</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/alfresco-ecm-core-api-returns-403/m-p/92190#M27326</link>
      <description>&lt;P&gt;Your OPTIONS request is not sending any authentication header with the ticket that I can see. So even though you have authenticated before, this call is again unauthenticated and thus a 403 is expected.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2020 14:01:51 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/alfresco-ecm-core-api-returns-403/m-p/92190#M27326</guid>
      <dc:creator>afaust</dc:creator>
      <dc:date>2020-04-24T14:01:51Z</dc:date>
    </item>
    <item>
      <title>Re: Alfresco ECM Core API returns 403</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/alfresco-ecm-core-api-returns-403/m-p/92191#M27327</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://migration33.stage.lithium.com/t5/user/viewprofilepage/user-id/16045"&gt;@afaust&lt;/A&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;How to resolve this error? Anything needs to be changed in ADF side? I have similar configuration in my ACS. I have allowed CORS with given filters. Still I'm getting 403 error. When I put cors.allowed.origin=*, I'm able to login. But, with specific IP/host, I'm getting 403.&lt;/P&gt;&lt;P&gt;Can you please let me know how to resolve this?&lt;/P&gt;</description>
      <pubDate>Wed, 23 Sep 2020 05:33:41 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/alfresco-ecm-core-api-returns-403/m-p/92191#M27327</guid>
      <dc:creator>jigir_shah</dc:creator>
      <dc:date>2020-09-23T05:33:41Z</dc:date>
    </item>
    <item>
      <title>Re: Alfresco ECM Core API returns 403</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/alfresco-ecm-core-api-returns-403/m-p/92192#M27328</link>
      <description>&lt;P&gt;How did you config IP/Host,you should configure it like following,please refer to&amp;nbsp;&lt;A href="https://tomcat.apache.org/tomcat-7.0-doc/config/filter.html" target="_blank" rel="noopener nofollow noreferrer"&gt;https://tomcat.apache.org/tomcat-7.0-doc/config/filter.html&lt;/A&gt;&lt;/P&gt;&lt;TABLE border="1" cellpadding="5"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;cors.allowed.origins&lt;/TD&gt;&lt;TD&gt;&lt;P&gt;A list of&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://tools.ietf.org/html/rfc6454" target="_blank" rel="noopener nofollow noreferrer"&gt;origins&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;that are allowed to access the resource. A&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;*&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;can be specified to enable access to resource from any origin. Otherwise, an allow list of comma separated origins can be provided. Eg:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://www.w3.org" target="_blank" rel="noopener nofollow noreferrer"&gt;https://www.w3.org&lt;/A&gt;, &lt;A href="https://www.apache.org" target="_blank" rel="noopener nofollow noreferrer"&gt;https://www.apache.org&lt;/A&gt;.&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Defaults:&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;The empty String. (No origin is allowed to access the resource).&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Thu, 24 Sep 2020 08:21:13 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/alfresco-ecm-core-api-returns-403/m-p/92192#M27328</guid>
      <dc:creator>kaynezhang</dc:creator>
      <dc:date>2020-09-24T08:21:13Z</dc:date>
    </item>
  </channel>
</rss>

