Embedded browser session - disable InPrivate?

Hello,

Thank you for reaching out regarding this.

I have a few questions which you can hopefully answer.

• Which version of RDM are you using?
• Which type of data source are you using?

I’m also wondering which entry type you're using? Are you using a "Web Browser (HTTP/HTTPS)" entry?

If so, you can go in your entry "Properties" under the "More Settings" section you can find the "Private session(Incognito)" option, would this be what you're looking for?

Let me know,

Best regards,

Hello,

RDM is the latest (2022.1.25.0) and I am using Web Browser (http/https).

But as I said this is an embedded session and there I don´t have the possibility to select incognito or not. This setting only appears when I change the display to external.

So it seems that embedded browser sessions are automatically private and there is no way to change this. When I try to log in I just get a message that my sign in is not possible at the moment and when I look at the error details the problem is that my device is not Azure AD registered. But this is not true as I am able to login manually when using Edge directly.

So the question is if it is possilble to change this behaviour for embedded sessions also to allow them to bei NOT private.

Brgds Andreas

Hello,

Thank you for your reply,

I'd like to confirm which "Web Browser" option you're currently using in the "General" section of your entry "Properties", from quickly testing on my end when using "Microsoft Edge" in "Embedded" display mode the option "Private Session (Incognito)" is available under the "More Settings" tab.

Perhaps you could provide me with a screenshot of your properties and of this error?

Let me know,

Best regards,

Hello,

I think you got me wrong. I am not missing the setting. When I go to More Options I have the "Private Session..." option which is unchecked. So from Settings side it is OK. I just ghought that embedded means the browser is running in a private session. Sorry for that confusion...

But when I open our M365 portal with an ebedded browser i am unable to login because the M365 portal does not recognize that my device is Azure AD Joined which is a prerequisite to be able to login.

So something seems to block the M365 portal to check if my device is Azure AD Joined. Maybe it is not related to "Private Session" - but it seems that a feature is disabled that is needed for this when running Edge embedded.

Brgds Andreas

Hello,

Thank you for your reply,

From my understanding, you would like to have the "Private Session" option enabled for your entries connecting to the M365 portal?

Unfortunately, it's not possible to have this enabled globally, Perhaps you could use a "Template" with this option enabled when creating entries for the "M365 Portal" this will ensure the "Private Session" option is enabled for these entries.

We have the following knowledge base article regarding templates: https://help.remotedesktopmanager.com/commands_creatingtemplates.html

Let me know,

Best regards,

Hello,

Sorry - no, I don´t want to make Private Session enabled by default. As I said, I maybe confused you because of my wrong assumption...

I don´t know how much you know about Microsoft 365 and Conditional Access Policies. With Conditional Access Policies you can control who and how access to Microsoft 365 ressources is allowed or not. In our case access to Microsoft 365 ressources is only possible from an Azure AD joined device. So if you are on a private owned computer, you are not able to login. When you open Edge the browser is "somehow" able to check this information and pass it to the webpage. And this mechanism seems to be missing when edge is opened embedded. And that is my question - is it somehow possible to remove that restriction from an embedded browser session?

Brgds Andreas

Hello,

Thank you for clarifying,

Do you also encounter this issue when using "Google Chrome" as the "Web Browser" in your "Web Browser (HTTP/HTTPS)" entry "Properties"?

I'm also wondering if you could provide me with a screenshot of this error?

Are you still on RDM 2022.1.25.0 or have you updated to 2022.1.27.0?

Let me know,

Best regards,