axway-developer-relations/griffin-app-opensource

The Axway Griffin App goes open source!

The Griffin App

The Axway Griffin App goes open-source!

---

• What is it?
• Features
• How do I get started?
  • Get started with Mobile App
  • Get started with API
• Questions or feedback?

---

---

What is it?

The Griffin App is a free, open-source mobile application and API developed by Axway to help you and your team transition back into the workplace in a safe and compliant way.

Features

• 📅   Built-in calendar for easily scheduling and coordinating in-office hours among teams
• 🔍   "Weekly view" of upcoming office capacity levels
• 🏙   Support for multiple office locations, each with different office hour policies and capacity limits
• 📈   Analytics dashboard for HR or other privileged users to view office traffic trends and set policies/limits for each office location
• 🎨   Easy customization for your logos, colors, and branding
• 🔒   App and APIs secured by OAuth SSO
• 🚀   Native iOS and Android support all-in-one (thanks to the wonderful team behind Axway Titanium)

How do I get started?

Get started with Mobile App

You can find the instructions for getting the Mobile App here.

Get started with API

The API instructions for configuration and deployment are here.

Questions or feedback?

We'd love to hear from you! If you can't find what you're looking for in our documentation or Developer Portal, feel free to reach out to us on Twitter @AxwayDev.

---

At Axway, we've already used this app to help our own teams return safely. Now, we want it to help the world. ❤

griffin-app-opensource's Issues

Authentication Mechanism - How does that work?

This open source project has a great structure that I'm still trying to wrap my head around.

I was able to run the API server, set up Axway MBaaS, and able to run the iOS/Android App.

However, I'm having issues understanding how Authentication works. The API backend (surprisingly) doesn't have any login authentication from the /apis/ folder.

The Mobile app opens a website to authenticate from oauth-base-url within tiapp.xml, I also realize that there is support for a few Authentication mechanisms like keycloak which I'm not familiar yet with:

let authenticationProvider;

const public_key = fs.readFileSync(`./keys/${turbo.OAUTH_PROVIDER}.pub`, `utf8`);

if (turbo.OAUTH_PROVIDER === `custom_oauth`) {

	authenticationProvider = AuthenticationOAuthProvider({
		baseUrl:        Ti.App.Properties.getString(`oauth-base-url`),
		tokenPath:      `/oauth/token`,
		defaultHeaders: { apikey: Ti.App.Properties.getString(`oauth-apikey`, ``) },
		client_id:      turbo.oauth_client_id,
		keyfile:        `/keys/${Ti.App.Properties.getString(`oauth-kid`, `default`)}.pub`,
		token:          turbo.app.data.auth_token,
	});

} else if (turbo.OAUTH_PROVIDER === `keycloak`) {

	authenticationProvider = new AuthenticationOAuthProvider(`code`, {
		callback_url: turbo.oauth_callback_url,
		client_id:    turbo.oauth_client_id,
		endpoints:    turbo.oauth_endpoints,
		public_key,
		token:        turbo.app.data.auth_token,
	});
}

turbo.authentication = new Authentication({ provider: authenticationProvider });

However if Axway's MBaaS is the backend DB:
1- Should I manually create the User? (does it happen on the Axway's portal back end?)
2- How would you be able to login from the App if Axway's MBaaS?

scripts section in package.json referencing node scripts which don't exist

Noticing that there are several commands under the scripts folder that fail as a result of the ./scripts folder not existing under ./mobile.

Example
"create:appinfo:ios": "node ./scripts/internal/publishing/create-appinfo-ios.js ${npm_package_titanium_environment} ${npm_package_version}",