Not exactly -- every action, even the generic one just printing out
text, built with firefly (by default) has a flag `require-adobe-auth:`
enabled to true. this means the action WILL expect an access token when
it's invoked. this access token is used by our validator to check
whether this user / service should have access to this action. (see docs
for more detail). There are two gated layers -- the first one is this.
The second one is we recommend only using the access token passed in to
We check whether the user has product context in their user profile. On
finer control, Analytics is interesting example! Unlike other APIs,
Analytics 2.0 allows 2 types of integration, OAuth and Service Account.
OAuth allows the developer to leverage user's individual user access
while Service Account grants access to all data. When an action is
invoked, by default, an access token is always required to authorize and
to authenticate your action. This access token is also use for any API
Hi @ursboller I think we do have some sample applications (see "Code
Labs" on this page
However, I don't think we have one showing top nav and route mapping
like the one you are asking for. I can share the feedback with our
enablement team and see if they have anything ready to share!In the
meantime -- perhaps some existing React tutorials around routing would
Hi @ursboller ,Looks like this is related to
to that question, we recommend practicing caution when considering a
solution to share data between applications as it can give users access
to data that they are not supposed to be able to see. In regards to the
file lib, it is tied to one namespace at the moment and doesn't allow
cross-namespace access. Sarah
Hi @ursboller Currently, access is granted based on the user's existing
product access. A user needs to have access to all the products used by
the app to access it. Let's say the app uses Analytics and Campaign, a
user needs to have access to both to be able to use the app.We'd love to
be able to offer more flexible and customizable access control -- but
that's definitely more on the future-looking side for us at the moment.
I'd suggest being on the more cautious side exploring workarounds at t...
@ursbollerhow about writing an "installation" or "update" script using
Adobe I/O CLI?You can ask users to 1) create credentials in Console and
generate a file, 2) run your script to install or to update the app
using those credentials.Other than bash script, this can also be done
with GitHub actions -- see
for some of the OOTB shared GitHub actions that we have created! The
users just need to set up the Git...
Hi @ursboller In our current release, each Firefly app can only be
deployed and accessed within the same organization. While we have
considered the ISV angle (where an ISV can build and sell an app / a
service to be used by multiple orgs), we currently don't have a timeline
for supporting this ootb. If you have immediate need to use the same app
for a few different orgs, you can potentially deploy the same code into
different organizations using different credentials. However, you will
need to m...
Hi @Sharma_Shruti Are you configuring the wsk cli or the aio cli?The
.env file only applies if you are configuring the Adobe I/O CLI. After
you create the `.env` file within the current working directory, update
it with your Runtime credential and save the file. When you are in this
directory, and type in `aio runtime property get`, all the values should
be automatically picked up and shown here. You can proceed to execute
any `aio runtime` commands, including deployment commands.