Unlock Rar File Without Password Online

[Danel Potvin]

What would really be beneficial to ArcGIS Online from my point of view, would be adding the possibility to share content with 'everyone' while using some form of basic password protection (password protected sharing for users without organizational account). Other cloud services (OneDrive for example) offer similar functionality. The lack of this functionality is pretty much what keeps me from using ArcGIS Online for sharing content.

Hi,

+1 to this comment. We'd be happy with even just a "security by obscurity" approach that only allows access to anyone with the link. As is it, the only way to share with users that don't have an organizational account is to make my content (and all the layer services) completely public AND indexed on AGOL. Needless to say, this does not sit well with clients, and has kept us from using AGOL for anything meaningful.

Cheers,
Ben

I want to do something similar but the last thing I want is for people to have to remember another username and password and have to log in each time they use the map. I want my AGS Online map to just open like a Google Map and be able to use it right away. Is that possible without making everything publicly shared?

I want to be able to share certain content with public users but not make the data public. I thought perhaps if I made a group then I could invite public users to join my group, but that doesn't work either because public users cannot join groups made by organizational account users.

Thus, the only other solution that I could come up with is to somehow make the data accessible with a user name and password so that I could invite public users to collaborate but not make the data public. However, this option does not seem to be currently available. Perhaps there is a widget out there I am not aware of?

You can limit access to hosted feature services (just like with AGS/on-premise services) to specific, shared AGOL maps and applications, without users needing to enter a username and password, by using the method described here:

There is some new functionality for hosted layers that went out with the December release that may address some of the issues outlined here. You can now create hosted feature layer views. With these you could keep the source data shared internally with your organization for editing and create a public view with editing revoked.

I have been at the Fed GIS conference this past week and I have heard the issue come up a few times. It would be great if there was a way to share AGOL content (like a story map) to a private audience outside of my organization (like a client or local partner), but without making the content completely public. I realize that this is similar to the "reduced pricing for viewer only accounts", but in many sectors (like international development and non-profit), it is unrealistic to expect a local partner to pay for something that they are only going to view one time for just a few minutes.

I tried the workflow to secure access to layers, but the option "a secure service was detected" does not come up! The service is not shared - it's private. So when I add it as a new web service where can I get that option and enter the credentials??

As far as ideas go.... Being able to invite social-media based AGOL public accounts to organizational groups, and then share specific apps/maps/layers with that group, would help a lot in some cases where we want to provide a map/app to some but not all of the public (and not go so far as using Hub). And this would provide an identity if they add/edit features in a crowdsource app. Some means for the public to automatically register their public account with a group would definitely help. Hopefully we'll see these types of capability soon.

We are trying to setup a self-service password reset for our users residing in on-premises AD but we do not have Exchange online. Is it even possible for us to setup SSPR with Azure AD Connect without involving Exchange at all?

Hi, Exchange is not relevant to SSPR. As long as you are syncing your on-premises AD to Azure AD with Azure AD Connect, and you have licences as per -us/azure/active-directory/authentication/concept-sspr-licensing then you should be good to go with this feature.

Yes, it is possible. If you want your on-prem users to be able to reset their passwords via the SSPR (i.e. Office 365 synchronises back to the on-prem AD ) then you will need an Azure P1 licence for that user.

The SSPR included in the Free version of Azure AD does not write-back to on-prem, it only changes the password in 365 - the next time AzureAD synchronises that password is changed back to the AD password.

Thanks for the reply!@HidMov Here is the situation, We do have P1 licenses for users but when I verify our custom domain in Azure from, let's say, xyz.onmicrosoft.com to xyz.com so that users can login with their current email addresses this poses issue with Microsoft Teams stop treating "xyz.com" as external address and will not allow invite to be sent for the meeting. Is there a workaround for this? So that Office 365 do not treat xyz.com as internal? Any help will be greatly appreciated!!

Hi, if you add your xyz.com domain into your M365 tenant, which it seems you have, then this is going to be considered as an internal / accepted domain within your environment. I am curious to understand why you would wish it to be considered external?

Hi @PeterRising, Let me try explain without confusing you, Since we do not have Exchange Online and do not wish to involve our current on-prem Exchange to any of Office 365 services, we want our users to still use Microsoft Teams for video conferencing purposes. Only handful of employees are currently using the Teams app and would like other employees within the organization to be invited for meetings. Now, currently users using Teams app has "xyz.onmicrosoft.com" email and password setup by Office 365 but If I add my custom domain "xyz.com" for SSPR then it poses two issues; In order to send the invite out to internal employees Teams cannot see "xyz.com" as external to have the "Invite" option available. Teams searches for email addresses for let's say a...@xyz.com and b...@xyz.com in it's own address book which is not there because Exchange online is not integrated. If I do sync a...@xyz.com and b...@xyz.com from our on-prem AD then Teams is not able to send an email invite to those above users since they do not have emails setup with Exchange online. If we do add an email for a...@xyz.com in the Azure AD then it posses another issue with email structure because now we have two emails for the same user - a...@xyz.com created by Exchange online and their own on-prem a...@xyz.com which is more confusing on which one to use.

OK, I see where you are coming from. My suggestion to you here would be to configure Hybrid Coexistence between you on-premises Exchange and Exchange Online. This way, you can add your custom domain into O365 and still use Teams with full functionality with your on-premises mailboxes.

Important: If you had a T-Mobile account in the past, such as a previous prepaid account or an account that was canceled, and you want to reuse the email from that account, use the steps for the Email already registered error.

For login issues, don't access your T-Mobile account online from a bookmark/favorites, try manually entering the website address and retry logging in. There is a limit of 30 login attempts in a 24-hour period. Business customers eligible for the Account Hub should use that instead of T-Mobile.com.

It's good practice to change account passwords every few months. T-Mobile will require that you change your T-Mobile ID password if we detect that this password was used on compromised websites not related to T-Mobile.

How do I get someone to fill in my form without having access to my username and Password? I want to send a link out to my participants to fill in their responses because I cannot go collect the data physically. So I want to send out a link that they can use to access the form and fill out.
So far this link to a form I made is asking the people to put in a username and password. BUT if I give them these details, wont they be able to log into my user profile and have access to my projects and even modify things? that is my worry. Help please!

The Exchange Online PowerShell module uses modern authentication for connecting to all Exchange-related PowerShell environments in Microsoft 365: Exchange Online PowerShell, Security & Compliance PowerShell, and standalone Exchange Online Protection (EOP) PowerShell. For more information about the Exchange Online PowerShell module, see About the Exchange Online PowerShell module.

REST API connections in the Exchange Online PowerShell V3 module require the PowerShellGet and PackageManagement modules. For more information, see PowerShellGet for REST-based connections in Windows.

Connect commands will likely fail if the profile path of the account that you used to connect contains special PowerShell characters (for example, $). The workaround is to connect using a different account that doesn't have special characters in the profile path.

With the EXO V3 module (v3.0.0 or later) and the demise of Basic authentication (remote PowerShell) connections to Exchange Online, you're using REST API cmdlets only. For more information, see REST API connections in the EXO V3 module.

When you use the ExchangeEnvironmentName parameter, you don't need use the ConnectionUri or AzureADAuthorizationEndPointUrl parameters. Common values for the ExchangeEnvironmentName parameter are described in the following table:

The DelegatedOrganization parameter specifies the customer organization that you want to manage as an authorized Microsoft Partner. For more information, see the connection examples later in this article.

c80f0f1006