Name of the app
The app this issue relates to.
MS Graph for SharePoint
Describe the bug
A clear and concise description of what the bug is.
Receiving error when running every action except test connectivity: Error from server. Status Code: 401 Data from server: InvalidAuthenticationToken. Lifetime validation failed, the token is expired.
Test Connectivity appears to be the only action utilizing the 'is_force' param and _make_rest_call_helper is not gracefully handling checking for an expired token and generating a new one
To Reproduce
Steps to reproduce the behavior:
- Generate client secret for Graph API
- Use secret until it expires
- Attempt any action besides test connectivity after secret expires
- Receive following error: Error from server. Status Code: 401 Data from server: InvalidAuthenticationToken. Lifetime validation failed, the token is expired.
- Only able to generate new token via test connectivity
Expected behavior
All actions handle generating new token if expired
Screenshots
If applicable, add screenshots to help explain your problem.
Splunk SOAR Version (please complete the following information):
- OVA, Unprivileged Install, or RPM? Unprivileged
- If not OVA, OS Version? CentOS 7
- Hypervisor (if applicable)? NA
- App Version? 1.2.0
Additional context
Add any other context about the problem here.
test connectivity appears to be the only action utilizing the is_force param to force generating a new token. Maybe the order of operations in _make_rest_call_helper is off and other actions are erroring and not generating a new token
Name of the app
The app this issue relates to.
MS Graph for SharePoint
Describe the bug
A clear and concise description of what the bug is.
Receiving error when running every action except test connectivity: Error from server. Status Code: 401 Data from server: InvalidAuthenticationToken. Lifetime validation failed, the token is expired.
Test Connectivity appears to be the only action utilizing the 'is_force' param and _make_rest_call_helper is not gracefully handling checking for an expired token and generating a new one
To Reproduce
Steps to reproduce the behavior:
Expected behavior
All actions handle generating new token if expired
Screenshots
If applicable, add screenshots to help explain your problem.
Splunk SOAR Version (please complete the following information):
Additional context
Add any other context about the problem here.
test connectivity appears to be the only action utilizing the is_force param to force generating a new token. Maybe the order of operations in _make_rest_call_helper is off and other actions are erroring and not generating a new token