Skip to content

missed signed file #560

Open
Open
@galaara98

Description

@galaara98

Describe the issue
in an environment that requires code signing
in powershell 7.5.0+
the lack of signed .ps1xml files causes inability to use module

To Reproduce
Steps to reproduce the behavior:

  1. powershell 7.5.0+
  2. set-executionpolicy allsigned (just to prove a point / demonstrate... we used remotesigned, but this module is in a network location)
  3. pspas version 6.4.85
  4. new-passession -parameters that should work
  5. red text

psPas.CyberArk.Vault.Account.Type.ps1xml ... is not digitally signed. You cannot run this script...

Expected behavior
no red text :P
would you mind signing that file (its the only one I am gettign an error on, but in theory i might not have interacted with one)

Screenshots & Console Output
If applicable, add screenshots and/or console output to help explain your problem.

<--Console Output Goes Here-->

Your Environment
Include relevant details about your environment

  • PowerShell Version:
  • psPAS Version:
  • CyberArk Version:

Additional context
Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions