scope update via application patch function not working
@andrueastman ci sta già lavorando.
Dal 19/2/2025.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Describe the bug
Since updating to Microsoft Graph SDK version 6.17.0, our functions for updating/patching an application's 'oauth2PermissionScopes' seem to be failing in our Kotlin app.
Java Version: 17
Kotlin Version: 2.1.0
For example, if I try to change the 'oauth2PermissionScopes' name from "Files.Read" to "Directory.Read," the response from the 'Application patch' function is null. I assume this is a good sign since, when I debug and intentionally cause an error, such as by using an incorrect application ID (or object ID), I do receive an error response.
executed code to patch application:
fun updateApplication(app: Application) {
try {
graphServiceClient.applications()
.byApplicationId(app.id)
.patch(app)
} catch (e: ApiException) {
...
}
}
applicationToUpdate.api.oauth2PermissionScopes JSON object:
[
{
"id": "1234abcd-12ab-12ab-12ab-123456abcdef",
"name": "Files.Read",
"type": "User",
"consentDisplayName": "Read your files",
"consentDescription": "Allows the application to read your directories"
}
]
However, when using version 6.16.0, the application’s 'oauth2PermissionScopes' are updated successfully after calling the patch function. In contrast, when performing the same operation with version 6.17.0, the 'oauth2PermissionScopes' remain unchanged (in this case, still showing "Files.Read").
Expected behavior
I'd expect, that the 'oauth2PermissionScopes' would be updated the same as in version '6.16.0'.
How to reproduce
- search a test application
- create an application object of the test application
- change the oauth2PermissionScopes name
- run the application patch function using the object id you copied and the application object copy you created
SDK Version
=> 6.17.0
Latest version known to work for scenario above?
6.16.0
Known Workarounds
No response
Debug output
Click to expand log
```</details>
### Configuration
_No response_
### Other information
_No response_
- Lingua principale
- Java
- Stelle
- 444
- Fork
- 154
- Merge medio
- 18h 28m
- PR unite (30g)
- 4
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoftgraph/msgraph-sdk-java
-
status:waiting-for-triage type:bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
microsoftgraph/msgraph-sdk-java#2610 ·
-
status:waiting-for-triage type:bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 55/100
microsoftgraph/msgraph-sdk-java#2656 ·
-
status:waiting-for-triage type:bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
microsoftgraph/msgraph-sdk-java#2654 ·
-
status:waiting-for-triage
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
microsoftgraph/msgraph-sdk-java#2639 ·
-
Error in PATCH onlineMeeting Apertastatus:waiting-for-triage type:bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
microsoftgraph/msgraph-sdk-java#2589 · 1 commento ·
Tutte le issue di microsoftgraph/msgraph-sdk-java
Issue simili
-
awaiting triage bug Causes friction Hop Gui P1 P2 Transforms
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
apache/flink-agents#1152 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
jenkinsci/blueocean-plugin#5417 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
objectionary/eo-graphs#75 ·