<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D50Z00008G7VYWSA3Okta Classic EngineIntegrationsAnswered2018-12-10T14:47:09.000Z2018-06-22T08:29:01.000Z2018-06-22T08:29:01.000Z
403 Forbidden Error in SP Client Object Model
SharePoint client object model code which was working earlier now throws 403 forbidden error after OKTA integration. Given below is sample code:

 

var xmlDocument = new XmlDocument();

                XDocument xdoc = new XDocument();

                string siteURL = "http://<site-collection-url> (http://%3csite-collection-url%3e)";

                using (ClientContext context = new ClientContext(siteURL))

                {

 

                    Uri siteURI = new Uri(siteURL);

                    Uri xmlDocURI = new Uri(" http://<site-collection-url>/XMLDocLibraryName/MegaMenu.xml (%20http:/%3csite-collection-url%3e/XMLDocLibraryName/MegaMenu.xml)");

                    string xDocURL = xmlDocURI.AbsoluteUri;

                   context.Credentials = new NetworkCredential(farm-account, farm-acc-pwd);                

                      context.ExecuteQuery();

                

                 ………………………….

                      }

 

It fails on ExecuteQuery and throws 403 forbidden error.

 

I guess OKTA will provide some kind of token to authorize these request. Do we have any API from OKTA which generates token?


This question is closed.
Loading
403 Forbidden Error in SP Client Object Model