I'm writing a PowerShell script to interact with our Chromebook inventory and I have followed the process outlined here
https://developers.google.com/admin-sdk/directory/v1/guides/delegation
To create a private key file and delegated it permissions.
However, there's no documentation how to decode the public/private key to generate a token without using one of the pre-built libraries, which of course don't include PowerShell. Even if there was a language agnostic description of what needs to be done I'd be able to try something out, but unfortunately there isn't.
I found this question which seems to be the same issue as what I'm having but it was never answered either.
Google Identity Platform: Using OAuth 2.0 in Powershell using Firebase Admin SDK private key
Try using a pfx rather than the JSON file and following the framework laid out here. Your scopes will be different but this should get you started.
I'm migrating from iText 5.5.5 to iText 7.0.2 and I noticed that class com.itextpdf.text.pdf.security.PdfPKCS7 which I use to work with certificates and signatures is gone. Is there equivalent of the class in iText7 or has it been completley reworked? If so, where did the functionality moved?
I got inspiration from https://github.com/abevoelker/pdf_ravager to create XFA Flattening. I was trying to use the XFAWorker, which is a paid version. I am trying to get the trial version to work with jRuby. XFAFlattener cannot be instantiated since it says that the class cannot be found. I added the license key as well. I am doing all the experiment in jirb.
I am assuming i dont understand how license key works. Any suggestions will be great.
I need to be able to view and edit a .sis file. Can anyone suggest the right way to do this please?
Basically, you could indeed extract stuff, modify them and re-pack them. there are tools that can help on this, for example SisContent claims to be able to do so, thus you could use this app at least for viewving the SIS.
Anyhow, the problem there is then the signing. If the app requires capabilities that are ok with Self-signing (and is not having any auto start feature etc.) then you could make own Self-signing certificate, either with the makekeys included in the SDK, or using OpenSSL. With SisContent, there also appears to be Self signing certificate included in it.
Anyhow note that following capabilities: ReadDeviceData, WriteDeviceData, PowerMgmt, ProtServ, SwEvent, SurroundingsDD, Trusted UI, CommDD, DiskAdmin, MultimediaDD, NetworkControl, CommDD, DiskAdmin, MultimediaDD and NetworkControl. Can not be used with self-signing, and as there is no ways on signing apps (and there were never a way on signing others apps) with real Symbian certificate having publicer ID. and thus these apps can not really be installed after they are modified.
Then again, if you are targeting for pre-3rd edition devices, then they are not requiring any signing, thus you could extract the files, modify them, and simply repack with makesis.
There is a software called unmakeSis.
I'm trying to use the NFC Plugin but i have an error "Signature could not verify". I write the code generating the signature of the data and a selfsigned certificate. But when I put all them together i shows me that error. Can you help me with this?
The Signature Record support is experimental at this point, so I advise you to check out the sources for a deeper investigation.