enable_jit_provisioning: false (#31)

* enable_jit_provisioning: false

* Updating README

README.md

@@ -10,17 +10,19 @@ How to set up a GitOps workflow to manage Fleet:
 
 1. Clone this repository.
 
-2. Make any changes to policies, queries, controls, and more defined in the files.
+2. If you do not have a Premium Fleet license, delete the `teams` folder.
 
-3. Create your own GitHub repository.
+3. Make any changes to policies, queries, controls, and more defined in the files.
 
-4. Add `FLEET_URL` and `FLEET_API_TOKEN` to your GitHub repository secrets.
+4. Create your own GitHub repository.
 
-5. Update the `env` section of your [.github/workflows/workflow.yml](https://github.com/fleetdm/fleet-gitops/blob/main/.github/workflows/workflow.yml) file for all the environment variables that are mentioned in your `default.yml` and `teams/*.yml` YAML files. For the environment variables that map to secrets, add the required secrets to your GitHub repository secrets.
+5. Add `FLEET_URL` and `FLEET_API_TOKEN` to your GitHub repository secrets.
 
-6. Push your cloned and modified code to your repo.
+6. Update the `env` section of your [.github/workflows/workflow.yml](https://github.com/fleetdm/fleet-gitops/blob/main/.github/workflows/workflow.yml) file for all the environment variables that are mentioned in your `default.yml` and `teams/*.yml` YAML files. For the environment variables that map to secrets, add the required secrets to your GitHub repository secrets.
 
-7. In GitHub, enable the `Apply latest configuration to Fleet` GitHub Actions workflow, and run workflow manually. Now, when anyone pushes a new commit, the action will run and update Fleet.
+7. Push your cloned and modified code to your repo.
+
+8. In GitHub, enable the `Apply latest configuration to Fleet` GitHub Actions workflow, and run workflow manually. Now, when anyone pushes a new commit, the action will run and update Fleet.
 
 #### Structure:
 

default.yml

@@ -34,7 +34,7 @@ org_settings:
     org_name: Fleet Device Management
   smtp_settings:
   sso_settings:
-    enable_jit_provisioning: true
+    enable_jit_provisioning: false
     enable_jit_role_sync: false
     enable_sso: true
     enable_sso_idp_login: false