Exchange ews call through sharepoint hosted app permission issue. Access is denied.


hello,

in 1 of posted question on forum saw mike facing same issue of passing credential ews exchange service through sharepoint hosted app, mike: able working. tried ajax post request , getting access denied on sharepoint hosted app. when try html file prompts me login , provided login fetches data otherwise unautherized 401 error inputs helpful thanks..

hi,

seems issue office 365 rather on-premise on-premise use ntlm authentication (and therefore wouldn't prompt - assuming user has rights ews).  it sounds ews supports oauth authentication there doesn't seem way of getting oauth token via javascript.

 

can ms advise on office 365 scenario (how authenticate ews via javascript user logged on sharepoint , account has rights ews)?  know can work around issue using "service/proxy account" (and supplying these credentials using basic authentication) isn't ideal user has rights ews , logged in shouldn't needed (and thought of sending usernames/passwords if service account doesn't sound idea - guess it's ok under https still...).

 

original post forum can found here:

 

http://social.msdn.microsoft.com/forums/en-us/appsforsharepoint/thread/6736f1d2-1560-4c88-9377-e13e508f1809

 

post exchange forum can found here:

 

http://social.technet.microsoft.com/forums/en-us/exchangesvrdevelopment/thread/00e5b8f2-ff8e-431d-a582-049196f1872a



SharePoint  ,  Apps for Office and SharePoint  >  Developing Apps for SharePoint 2013



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more