You had recently allowed some third-party music apps to access your Apple Music and the media library. But due to some personal reasons, you have decided to revoke the access and hence looking for a quick way to de-authorize third-party app permissions for Apple Music.
Beginning with macOS 10.13 and for all subsequent macOS releases, Apple has been tightening the permissions granted to third-party applications, and requiring end users (you) to explicitly allow these applications access to things like the microphone, video camera, hard drive, and macOS accessibility services. Beginning with macOS 10.13 and for all subsequent macOS releases, Apple has been tightening the permissions granted to third-party applications, and requiring end users (you) to explicitly allow these applications access to things like the microphone, video camera, hard drive, and macOS accessibility services. And the permissions to the folder I used initially. Drwxrwxrwx 2 roh21 108 2048 Jun 23 06:32 startup I curious as to why I could not change the permissions to the startup folder even after multiple attempts with the chmod -R option. Also, note that I was using Mac OS X in my school's library.
Fret not! Apple lets you perfectly manage app permissions for the music service. Moreover, you can get it done both from the iOS device and Mac/PC with ease. Let me walk you through the steps:
How to Revoke Third-Party App Access to Apple Music on iPhone and iPad
Step #1. Launch Settings app on your iOS device → Tap on iTunes & App Store.
Step #2. Now, tap on your Apple ID and select View Apple ID in the popup.
Step #3. Now, you need to enter your Apple ID password or use Touch/Face ID to authenticate.
Step #4. Next, head over to the App Permissions section.
Note: In case you haven’t yet authorized any apps, App Permissions section won’t appear.
Step #5. Choose the service that you no longer want to have access to your media library.
Step #6. Next up, locate the third party app and then swipe left on it.
Step #7. Finally, tap on Delete.
That’s it!
Alternately,
Step #1. Head over to Settings → Tap on Privacy.
Step #2. Tap on Media & Apple Music.
Step #3. You should see all the apps that had requested access to the music streaming service, video activity, and media library. Simply turn off the switch next to each app which you want to prevent from using your data.
How to Remove a Third Party App Access for Apple Music from your Mac or PC
Step #1. Launch iTunes on your computer.
Step #2. Now, click on Account menu and select View My Account. Then, you have to enter your password and hit Return.
Step #3. On the Account Information page, go to the App Permissions section. Click on Manage next to Apple Music.
Note: In case, you haven’t authorized any apps, App Permissions section will not show up.
Step #4. Finally, locate the app and click on Remove.
That’s all folks!
Over to you
So, that’s how you can ideally manage app permissions for the music streaming service. Have any question? Shoot it in the comments.
You might want to take a peek at these posts as well:
The founder of iGeeksBlog, Dhvanesh, is an Apple aficionado, who cannot stand even a slight innuendo about Apple products. He dons the cap of editor-in-chief to make sure that articles match the quality standard before they are published.
Home > Articles > Apple > Operating Systems
␡
< BackPage 7 of 11Next >
This chapter is from the book
Apple Training Series: Mac OS X Support Essentials v10.6: A Guide to Supporting and Troubleshooting Mac OS X v10.6 Snow Leopard
This chapter is from the bookThis chapter is from the book
Apple Training Series: Mac OS X Support Essentials v10.6: A Guide to Supporting and Troubleshooting Mac OS X v10.6 Snow Leopard
Managing Permissions via Command Line
Viewing and modifying file system permissions in the command line is both much richer and more complicated than in the Finder. The Finder has streamlined ownership, permissions, and ACLs, providing only the most common features that users require. However, the command line offers every conceivable ownership and permissions option. Further, the command line often provides more than one method for performing identical permissions tasks.
Viewing Traditional UNIX Permissions
Once again, the ls command is your primary tool for viewing file and folder information in the command line. The ls command has many options for viewing nearly any file or folder attribute. You can learn more about all the options available to ls from its manual entry page. Here, you will be presented with a few fundamental permissions viewing options.
The most basic ls option for viewing file and folder ownership and permissions is –l:
The first string of characters at the beginning of each line is shorthand for the item type and permissions. The following information appears from left to right: the number of hard links associated with the item (for most users, this particular bit will be trivial information), the assigned owner, the assigned group, the last modification date, and finally the item’s name.
The syntax for the abbreviated information section is:
![]()
The execute privilege attribute x has not been introduced yet, but it is the third standard UNIX privilege attribute after read and write. The execute privilege is enabled on files that are commands and applications (or folders that contain application bundles), to indicate that the item contains executable software code. The execute privilege is also required on normal folders to access the contents of the folder. The Finder doesn’t show you when the execute privilege is used, but it will properly manage the execute privilege when you make permissions changes using the Get Info window.
Viewing Access Control Lists (ACLs)
The ACL technology is more advanced than traditional UNIX-style permissions because it allows for an arbitrary number of user and group permissions rules per item. Each permissions rule is known as an Access Control Entry (ACE). Every file and folder on the system can have an unlimited list of ACE rules, hence the “list” in ACLs.
From the command line, Mac OS X’s ACL implementation provides more than a dozen unique privilege attribute types and lets you define each as a specific allow or deny rule. In other words, you can assign an item an unlimited number of user or group rules, or ACEs, which can be used to allow or deny any of the following privilege attributes:
Furthermore, each ACE for a folder can include a static inheritance rule that defines whether the folder’s permissions also apply to new items placed in the folder. Inheritance attributes include the following: no inheritance, apply to just new items in this folder, apply to any new child folders, apply to any new child files, and apply to all descendants of this folder.
To view an item’s ACLs alongside their permissions, simply add the -e option to the -l option:
Modifying File Permissions via Command Line
You will use two primary commands for changing file and folder permissions in the command line: chown for changing ownership and chmod for changing privileges.
Changing Ownership via Command Line
Short for “change ownership,” chown will let you change the owner and group associated with a file or folder. Using chown often requires root access, so this command is almost always preceded by the sudo command. To use chown, enter the new owner’s name, followed optionally by a colon and the new group name, and then finish with the item’s path. In the following example, Michelle will use the chown command to change testfile1’s ownership to the user account “kevin” and the group account “admin.”
Changing Privileges via Command Line
Short for “change file mode,” chmod will let you change the privileges associated with a file or folder. Using chmod on files you don’t own requires root access, so the chmod command is often preceded by the sudo command. To use chmod, enter the new privileges first followed by the item’s path.
As for changing privileges, there are two basic methods when using the chmod command:
Change App Permission Mac Software
In the following example, Michelle will use the chmod command to change the permissions of testfile1 and testfolder to allow read and write access for the owner and the group but read-only access for everyone else. She will first use alphanumeric abbreviations, and then octal privilege equivalents.
![]() Using the Sticky Bit
As mentioned previously in this chapter, the /Users/Shared folder has a unique permission setting that allows all local users to read and write items into the folder yet prevents other users from being able to delete files that they didn’t originally put in this folder. This special permissions configuration is brought to you courtesy of the “sticky bit.” Essentially, enabling the sticky bit on a folder defines it as an append-only destination, or, more accurately, a folder in which only the owner of the item can delete the item.
You can clearly see the sticky bit setting of the /Users/Shared folder when you view its ownership and permissions. Note the t on the end of the permissions information, which indicates that the sticky bit is enabled:
You can enable sticky bit functionality similar to the /Users/Shared folder on any other folder using a special octal notation with the chmod command. In the following example, Michelle has already created a new folder named NewShared. She then uses the chmod command with +t to set sharing for all users with sticky bit functionality:
Managing Locked Items via Command Line
As mentioned previously, Mac OS X includes a special file system lock feature that prevents anyone but the owner of an item from making changes to that item. Any user can easily lock a file or folder he owns from the Finder’s Get Info window, also covered earlier in this chapter.
The problem with the file system lock is that the Finder prevents even other administrative users from making changes or even unlocking items they don’t own. In fact, this file system lock extends to the command line as well. Even with sudo access, an administrator is not allowed to change a locked item—with one important exception, the chflags command. This command allows the administrator to change file system flags, which among other things allows you to lock or unlock any file or folder on the system.
In the following example, Michelle needs to change the permissions of a folder owned by another user so the folder can be shared. However, even using sudo she is denied access from doing this, indicating the file is locked. She verifies this by using ls –lO to view the file listing with file flags, which indeed returns that the folder is locked, “uchg”. She then uses the chflags command with the nouchg option to unlock the folder. Finally, she is able to make changes to the previously locked file.
Related Resources
Change App Permission Mac Install
Change File Permissions Mac Terminal
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |