You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 19, 2021. It is now read-only.
I submitted a bug (#2890) but it has gotten zero attention, so maybe that's the wrong place. Here is what I am experiencing, from the bug text:
Calling Get-PnPApp (or other ALM cmdlets) with a connection opened with the switch -UseAdfs or no switch (Windows claims) does not work. The connection opens correctly and other PnP cmdlets work fine, but the ALM cmdlets do not work. They either give an Access denied error or a 403 Forbidden error.
If you open a connection with the same user account first, using -UseWebLogin, the Get-PnPApp and other ALM calls succeed. Then if you open a new connection with -UseAdfs, the ALM cmdlets also succeed unless/until you clear the internet cache for that user account in Windows (or presumably a cookie expires or other persistent artifact from the web login approach).
This is SharePoint 2019 on-premises. Both the PnP 2019 and the PnP for SPO were tried, just to see if they would behave differently. They behave the same.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, all,
I submitted a bug (#2890) but it has gotten zero attention, so maybe that's the wrong place. Here is what I am experiencing, from the bug text:
Calling Get-PnPApp (or other ALM cmdlets) with a connection opened with the switch -UseAdfs or no switch (Windows claims) does not work. The connection opens correctly and other PnP cmdlets work fine, but the ALM cmdlets do not work. They either give an Access denied error or a 403 Forbidden error.
If you open a connection with the same user account first, using -UseWebLogin, the Get-PnPApp and other ALM calls succeed. Then if you open a new connection with -UseAdfs, the ALM cmdlets also succeed unless/until you clear the internet cache for that user account in Windows (or presumably a cookie expires or other persistent artifact from the web login approach).
This is SharePoint 2019 on-premises. Both the PnP 2019 and the PnP for SPO were tried, just to see if they would behave differently. They behave the same.
Beta Was this translation helpful? Give feedback.
All reactions