1. Sign on to the Oracle Cloud Infrastructure Console as a tenancy administrator.
2. Open the navigation menu and select Identity & Security → Identity → Domains → <YourDomain> -> Groups → Create Group.
3. Create a group, for example ocifn_grp: For details on how to create a group see To create a group.
4. Select Identity & Security → Identity → Domains → <YourDomain> → Users → Create user.
5. Create a user, for example ocifn_user: For details on how to create a user see To create a user.
6. Select Groups → Assign user to groups.
7. Assign ocifn_user to the group: For details on how to add a user to a group see To add a user to a group

1. Sign on to the Oracle Cloud Infrastructure Console as a tenancy administrator.
2. Open the navigation menu and select Identity & Security → Identity → Compartments.
3. Select Create Compartment and add a compartment, for example ocifn_compartment: For details on creating a compartment see To create a compartment

1. Sign on to the Oracle Cloud Infrastructure Console as a tenancy administrator.
2. Open the navigation menu and select Networking → Virtual cloud networks.
3. Select Start VCN Wizard to create a new VCN.
4. In the dialog, select Create VCN with Internet Connectivity and click the Start VCN Wizard.
5. In the wizard, enter the following details:
   1. VCN Name: Enter the VCN name, for example ocifn_vcn.
   2. Compartment : Enter the compartment within which the VCN resources will be created, for example ocifn_compartment.
6. Click Next, then click Create to create the VCN and related network resources.

1. Sign on to the Oracle Cloud Infrastructure Console as a tenancy administrator.
2. Open the navigation menu and select Identity & Security → Key Management & Secret Management
3. Click Create Vault.
4. Select the compartment into which the Vault will be created, and give the Vault a Name. Click Create Vault.
5. Open the Vault you created and click Create Key. Create the Key in the same compartment you created your Vault. Give the Key a name and click Create Key.
6. From the Resources menu, select Secrets. Click Create Secret.
7. On the Create Secret page, add details for compartment, name, and description. Select the key you created from the Encryption Key drop down list. Select the Manual secret generation option, and enter your client code and client secret in one of the following formats into the Secret Contents field.
   1. OAuth-based Authorization

      {
        "clientCode": "69b48365-14e2-430a-bd75-171f89c158fa",
        "clientSecret": "*/Z9g:gM*SWWLLCGkQhQg2hdWelAZD82"
      }

      For sample code to create authorization token for OAuth-based authorization, see OAuth Authorization - Sample Token Creation Code.
   2. Basic Authorization

      {
        "username": "69b48365-14e2-430a-bd75-171f89c158fa",
        "password": "*/Z9g:gM*SWWLLCGkQhQg2hdWelAZD82"
      }

      .
   For sample code to create authorization token for Basic authorization, see Basic Authorization - Sample Token Creation Code
8. Select Create Secret to save your changes.

secretId: "ocid1.vaultsecret.oc1.iad.dyyyyehdl4ggaawnqt47hfj48ltofzkdg6wy5fjne859jg0"
region: "us-ashburn-1"

ALL { resource.type = 'fnfunc', resource.compartment.id = 'ocid1.compartment.oc1..fdfdfege4om6nat7fue56566556qqvj3eesjqhmjaegeiaxa' }

1. Sign on to the Oracle Cloud Infrastructure Console as a tenancy administrator.
2. Open the navigation menu and select Identity & Security → Identity → Policies.
3. Select Create Policy, specify a name for the policy, for example ocifn_policy, and select the tenancy's root compartment.
4. Add a policy statement similar to:

   Allow dynamic-group <dynamic-group-name> to read secret-family in tenancy

1. Sign on to the Oracle Cloud Infrastructure Console as a tenancy administrator.
2. Open the navigation menu and select Identity & Security → Identity → Policies.
3. Select Create Policy, specify a name for the policy, for example ocifn_policy, and select the tenancy's root compartment.
4. Using Policy Builder, select Functions from the Policy use cases list, and base your policy on the Let users create, deploy, and manage functions and applications template.
5. Select the group created earlier, ocifn_group and the ocifn_compartment for the location. This should give you a policy statement similar to:

   Allow group 'Default'/'ocifn_grp' to use cloud-shell in tenancy
   Allow group 'Default'/'ocifn_grp' to manage repos in compartment ocifn_compartment
   Allow group 'Default'/'ocifn_grp' to read objectstorage-namespaces in tenancy
   Allow group 'Default'/'ocifn_grp' to manage logging-family in compartment ocifn_compartment
   Allow group 'Default'/'ocifn_grp' to read metrics in compartment ocifn_compartment
   Allow group 'Default'/'ocifn_grp' to manage functions-family in compartment ocifn_compartment
   Allow group 'Default'/'ocifn_grp' to use virtual-network-family in compartment ocifn_compartment
   Allow group 'Default'/'ocifn_grp' to use apm-domains in compartment ocifn_compartment
   Allow group 'Default'/'ocifn_grp' to read vaults in compartment ocifn_compartment
   Allow group 'Default'/'ocifn_grp' to use keys in compartment ocifn_compartment
   Allow service faas to use apm-domains in compartment ocifn_compartment
   Allow service faas to read repos in tenancy where request.operation='ListContainerImageSignatures'
   Allow service faas to {KEY_READ} in compartment ocifn_compartment where request.operation='GetKeyVersion'
   Allow service faas to {KEY_VERIFY} in compartment ocifn_compartment where request.operation='Verify'

1. idm-agcs-serverless-getting-started-sample: This is a basic and easy-to-understand sample with minimal code, demonstrating how functions work. This use case is ideal for customers needing to integrate a single application with the Generic REST connector, requiring minimal configuration. Initial set up is with an Oracle Identity Cloud Service (IDCS) application. Detailed steps to configure and deploy this function can be found in the `README.md` file within this directory.
2. idm-agcs-serverless-idcs-application-sample: This sample focuses on the IDCS application example with minimal configuration. It includes the framework to add more applications in the future within this function. Configuration and deployment steps are detailed in the `README.md` file located in this directory.
3. idm-agcs-serverless-azuread-application-sample: This sample is specifically for customers who need an AzureAD application example with minimal configuration. It contains the framework to add more applications in the future within this function. Detailed steps to configure and deploy this function are available in the `README.md` file inside this directory.
4. idm-agcs-serverless-multi-application-sample: This sample is for customers needing both IDCS and AzureAD application examples with minimal configuration. It includes the framework to add more applications in the future within this function. The `README.md` file in this directory provides all necessary steps to configure and deploy this function.

1. Develop tests following the example outlined below:
   grc-test-infra sample test

   package com.oracle.idm.agcs.grc.fn.test.infra;
    
   public class RequestResponseTemplateValidationTest {
    
       public void validateSearchUserAsIdentityRequestResponseTemplate() throws IOException, URISyntaxException, InterruptedException {
           // Get the configured Request template by passing the connectedSystem Name, entity name, and operation
           RequestTemplateOutput requestTemplate = getRequestTemplateOutput(connectedSystemName, UserAsIdentityEntity, Operation.SEARCH);
            
           // Get the configured Response template by passing the connectedSystem Name, entity name, and operation
           ResponseTemplateOutput responseTemplate = getResponseTemplateOutput(connectedSystemName, UserAsIdentityEntity, Operation.SEARCH);
            
           // Pass the required attributes in the request template by putting them in the attribute map
           HashMap<String, Object> attributesMap = new HashMap<>();
            
           // Call the generic utility method to validate request and response template
           Map<String, Object> lastRecord = processAndValidateRequestAndResponseTemplate(requestTemplate, responseTemplate, attributesMap);
            
           // Retrieve the necessary data from the response for further processing
           userAsIdentityUid = ((ArrayList<String>) lastRecord.get("uid")).get(0);
       }
   }

   • The first line inside the test is to get the configured Request template by passing the connectedSystem Name, entity name, and operation.
   • The second line gets the configured Response template using similar parameters.
   • Users need to pass the required attributes in the request template by putting them in the attribute map.
   • Then, users just need to call the generic utility method processAndValidateRequestAndResponseTemplate, which internally validates both the request and response templates for correctness by invoking the API and mapping its response with the configured response template.
   • The test will pass if the configured request and response templates are correctly configured; otherwise, it will fail, allowing users to see the failure reason and correct the templates accordingly.

   The example test file can be found in the sample implementation at the following location: <SampleBase>/grc-test-infra/src/test/java/com/oracle/idm/agcs/grc/fn/test/infra/RequestResponseTemplateValidationTest.java

2. Add the following prerequisites before running the test:
   1. Update the <SampleBase>/grc-test-infra/src/test/resources/config file with the following values for your environment:

      [DEFAULT]
      user=<<USER>>
      fingerprint=<<FINGERPRINT>>
      key_file=<<PEM_FILE_RELATIVE_PATH>>
      tenancy=<<TENANCY>>
      region=<<REGION>>

   2. Update the <SampleBase>/grc-test-infra/src/test/resources/config.properties file with the following value for your environment:

      connectedSystemName=<connectedSystemName>

   3. Add the private SSH key (.pem file) for the API Signing Key to the following location:

      <SampleBase>/grc-test-infra/src/test/resources/oci_api_key.pem

3. Execute the developed test and build the function:
   1. Navigate to the functions directory of the sample implementation.
   2. Compile and package the functions

      mvn clean package-DisDevMode=true