-
Notifications
You must be signed in to change notification settings - Fork 0
Implements CRUD event operations. #13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Creates a new project with an asp net core api application using https, no authentication and docker disabled
… for the api to use.
Someone with the right permissions needs to do a POST call to https://graph.microsoft.com/v1.0/schemaExtensions Also I think type Boolean is not allowed for targetType event schema extension. Which is why we might have to change requiredPhotoAgreement #1
Starting from scratch to use [resource owner password credential flow](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth-ropc) Additional resources of interest: 1. https://docs.microsoft.com/en-us/azure/azure-functions/functions-dotnet-dependency-injection 2. https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-desktop-acquire-token?tabs=dotnet#b2c-specifics 3. https://github.com/Azure-Samples/active-directory-dotnetcore-console-up-v2
…s public client in AAD under authentication
#3 Still need to do testing and figure out how we want to restrict the api in the regard which parts of the graph events we want to expose.
I got Username/Password flow to work by removing all permissions the application had in Azure and adding them back.
Removes all the code where I tried to get the graph authentication working.
To be able to have the schema extension as a type inside the event the MCCEvent can be created from an Outlook Event.
Found solution to Problem where casting additional data to the EventSchemaExtension object from JObject did not work. However, JObject has a conversion method.
… expose to the event engine api.
Add documentation.
Could you please provide Build instructions to start the project locally or an URL to an endpoint where the code is deployed? |
The code is not yet deployed because it needs to be secured first.
When running it if you get an error along the lines of Please let me know if there are any issues. |
Please specify that .net core 3.1 is required to run the program (had errors when trying to run func build with .net core 2.2). I now get the following error: Microsoft.CampusCommunity.EventEngine.Api: Method not found: 'Microsoft.Extensions.DependencyInjection.IServiceCollection Microsoft.Azure.Functions.Extensions.DependencyInjection.IFunctionsHostBuilder.get_Services()'. Steps to reproduce:
Host Machine: Any hints on how to proceed? |
I have no idea. |
Sorry for the long delay. These steps have worked for me:
To the actual functionality:
Please add this to the documentation. |
I am glad it finally worked. Sorry for the inconvenience.
|
Please provide a documentation on this before you merge it back into master. A good inspiration for this is https://commasto-api-dev.azurewebsites.net/swagger/index.html, but you can also write a markdown page explaining URLs, allowed query parameters, necessary body input and possible responses from the API. |
#14 is on the TODO list |
Preparations
Please check if the PR fulfills these requirements
🎫 Description
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
feature
What is the current behavior? (You can also link to an open issue here)
Current behavior is not applicable because the application did not exist before.
What is the new behavior (if this is a feature change)?
Add CRUD operations against Microsoft Graph for MCC events.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No
Other information:
🔒 Closes
Which issue(s) is (are) being closed by the PR?
#3