hello is it possible to create a login form from my web app, them connect it to login.microsoft.com without living my page to verify users credential? Thanks.
From the CrowdStrike article, “All requests to the Activities API must include an Authorization header. Requests that do not include a valid credential will result in an HTTP 403 Unauthorized response.” Verify you are using valid credentials, and make sure you are using the access OAuth token.
I tried another Microsoft email account (live.com) and made sure to use a fresh access OAuth token specific for the live.com account. Still getting the same 403 error. I wonder what I’m messing up or if Microsoft disabled the Activities API.
N Long Hmm... I have not tried a Live account. Can you create a new Outlook.com account and test with it to see if you get the same error? Of course, this is primarily designed to work with Office 365 tenants, which would be the true way to test (provided the account with which you are testing has the proper permissions to access the mailbox with which you are testing.)
I really appreciate your effort to teach like this, huge respect to you Sir
hello is it possible to create a login form from my web app, them connect it to login.microsoft.com without living my page to verify users credential? Thanks.
NSA is watching you!
solidPain90 Good - hope they enjoy the channel. Job offers welcomed. ;)
Ran the script and got "HTTP 403: AppId: "0000000040160CFB" is not allowed". Any ideas??
From the CrowdStrike article, “All requests to the Activities API must include an Authorization header. Requests that do not include a valid credential will result in an HTTP 403 Unauthorized response.” Verify you are using valid credentials, and make sure you are using the access OAuth token.
I tried another Microsoft email account (live.com) and made sure to use a fresh access OAuth token specific for the live.com account. Still getting the same 403 error. I wonder what I’m messing up or if Microsoft disabled the Activities API.
N Long Hmm... I have not tried a Live account. Can you create a new Outlook.com account and test with it to see if you get the same error? Of course, this is primarily designed to work with Office 365 tenants, which would be the true way to test (provided the account with which you are testing has the proper permissions to access the mailbox with which you are testing.)